Skip to content
This repository has been archived by the owner on Apr 18, 2021. It is now read-only.

Don't treat no-cache as no-store #18

Open
PSUdaemon opened this issue Aug 5, 2015 · 1 comment
Open

Don't treat no-cache as no-store #18

PSUdaemon opened this issue Aug 5, 2015 · 1 comment
Labels

Comments

@PSUdaemon
Copy link
Contributor

https://httpwg.github.io/specs/rfc7234.html#rfc.section.5.2.2.2

no-cache in a response means you can still store on your proxy, you just cannot serve it without revalidation. We should store the content but immediately expired. Then revalidate it upon request.

I can work on a patch for this if you would like.

@lox
Copy link
Owner

lox commented Aug 6, 2015

Ah yup, I think I have a branch somewhere that addressed this, but I can't find it. PR's welcome.

@lox lox added the bug label Feb 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants