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

fix wrong explanation about cache-control and authroization header #29064

Merged
merged 3 commits into from
Sep 15, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
fix wrong explanation about cache-control and authroization header
  • Loading branch information
Jxck committed Sep 12, 2023
commit 0c1f4fbe16d822685b72cb9b34029d22da812270
2 changes: 1 addition & 1 deletion files/en-us/web/http/caching/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Cache-Control: private

Personalized contents are usually controlled by cookies, but the presence of a cookie does not always indicate that it is private, and thus a cookie alone does not make the response private.

Note that if the response has an `Authorization` header, it cannot be stored in the private cache (or a shared cache, unless `public` is specified).
Note that if the response has an `Authorization` header, it cannot be stored in the shared cache by default unless some other explicit directives (e.g. `public`, `max-age` etc) are specified.
Jxck marked this conversation as resolved.
Show resolved Hide resolved

### Shared cache

Expand Down