Skip to content
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

Difficult to understand a sentence in Private Cache section #17199

Closed
aakashsardana opened this issue Jun 12, 2022 · 2 comments · Fixed by #17214
Closed

Difficult to understand a sentence in Private Cache section #17199

aakashsardana opened this issue Jun 12, 2022 · 2 comments · Fixed by #17214
Labels
Content:HTTP HTTP docs needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.

Comments

@aakashsardana
Copy link

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching

What specific section or headline is this issue about?

Private Caches

What information was incorrect, unhelpful, or incomplete?

In the Private Caches section there is a sentence

If the response has an Authorization header, it cannot be stored in either the private cache or the shared cache, even if it has max-age — and public can be used to allow such a case

The first half of the sentence is clear but I am not able to understand this-:

— and public can be used to allow such a case

Does it means that if we specify public when there is Authorization header then the response would be stored in a shared cache?

What did you expect to see?

Not able to understand the sentence mentioned above. A bit more clarity on this would be helpful

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details
@github-actions github-actions bot added Content:HTTP HTTP docs needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jun 12, 2022
@hamishwillee
Copy link
Collaborator

Thanks, yes it is confusing. Fixed by #17214

In summary, the text means that you can use public to make a response be stored in a shared cache even if the Authorization header is set.
IMO the problem with all this text is that it is irrelevant to using the private directive, which is what the section is about. I stripped it out and moved the comment on using public to where the information on public is located.

@aakashsardana
Copy link
Author

Yes now it is pretty much clear. Thanks @hamishwillee 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:HTTP HTTP docs needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants