Browser Cache —> no cache, why?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Harshad

    (@bornforphp)

    @jalo399 Can you please try to purge the cache and then try to manually preload it from WP-Optimize > Cache and check if it works?

    Hi @jalo399,

    Despite what it sounds like, the cache-control value of no-cache doesn’t mean that the browser won’t cache the page.
    Instead, it means that the browser should check with the server if it can serve a cached page, or should re-download it.

    See the doc here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control:

    no-cache: The response may be stored by any cache, even if the response is normally non-cacheable. However, the stored response MUST always go through validation with the origin server first before using it, therefore, you cannot use no-cache in-conjunction with immutable. If you mean to not store the response in any cache, use no-store instead. This directive is not effective in preventing caches from storing your response.

    This is used in conjunction with the 304 Not Modified response header.

    Also note that Cloudflare may override some of the headers.

    Marc.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Browser Cache —> no cache, why?’ is closed to new replies.