• Resolved Anonymous User 20443167

    (@anonymized-20443167)


    I need no-cache header without no-store.

    no-cache and no-store are 2 different things:

    Note that no-cache does not mean “don’t cache”. no-cache allows caches to store a response but requires them to revalidate it before reuse. If the sense of “don’t cache” that you want is actually “don’t store”, then no-store is the directive to use.

    If you want caches to always check for content updates while reusing stored content, no-cache is the directive to use. It does this by requiring caches to revalidate each request with the origin server.

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

    Please add a no-cache Cache Control option to the settings.

    • This topic was modified 3 years, 3 months ago by Anonymous User 20443167.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Anonymous User 20443167

    (@anonymized-20443167)

    With no-store you are saying don’t store cache.
    With no-cache you are saying cache, but ping the server for changes.

    You can’t send both rules together as if they were the same, they are pretty much opposite.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hey @poorjob

    Thank you for reaching out.
    I’ve created a GitHub issue on your behalf for this and we’ll remove no-store in future releases.

    Thank you for your patience.

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

The topic ‘I need “no-cache” header without “no-store”’ is closed to new replies.