New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public and Private vs. the world #320
Comments
The text in question for private:
I think there are two problems here:
I think this can be addressed by replacing the clause above with something like "subject to the other requirements in [ref to section 3]", and repeating it in the second paragraph. We'd also need to add |
For public, we have:
Similar to above, I think it should be "subject to the constraints defined in [ref to section 3]. A note like this would also help:
|
The language for
Cache-Control: public
andprivate
indicates that they override the rest of the caching model unconditionally; as discussed in #319, that is too broad.Also,
public
is often used even though the message is still cacheable, because developers misunderstand its semantics.The text was updated successfully, but these errors were encountered: