The cache-control does not have no-cache directive

Hello,
no-cache Browser Cache option causes the addition of as many options as possible that blocks caching, and it contains no-cache between them:

Header set Cache-Control: "max-age=0, private, no-store, no-cache, must-revalidate"

@vmarko yes that is what I am trying to say.
"max-age=0, private, no-store, no-cache, must-revalidate" is not no-cache directive. It is in-fact no-store.The no-cache directive must force caches to submit the request to the origin server for validation before releasing a cached copy.

Please read my previous comment and if possible please speak with the developers about this issue. It is shame that a super plugin like this has a misleading options and does not provide all the browser cache directives.

More about cache-control directive @ https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control

• This reply was modified 5 years, 10 months ago by thapa.laxman.

Hello,

Naming may be misleading. Our no-cache should be “don’t cache”, but it was renamed so it doesn’t interfere with cache control terminology.
no-cache alone doesn’t provide stable functionality across the browsers and based on our practice is not usable.