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

Jump to bottom

Very Old Warnings #660

Closed
mnot opened this issue Jan 7, 2021 · 1 comment · Fixed by #667
Closed

Very Old Warnings #660

mnot opened this issue Jan 7, 2021 · 1 comment · Fixed by #667
Assignees
@mnot
Labels
caching has-proposal

Comments

@mnot
Copy link
Member

mnot commented Jan 7, 2021

Note: Some HTTP/1.0 caches might not implement Cache-Control.

Is this warning still relevant? If we want to keep it, I think we need to qualify it; e.g., "A few old HTTP/1.0 caches that are unlikely to be used on the open Internet..."

Similar text in cc: no-cache.
@mnot mnot added the caching label Jan 7, 2021
@mnot mnot self-assigned this Jan 7, 2021
mnot added a commit that referenced this issue Jan 8, 2021
@mnot
Even HTTP/1.0 caches now support Age and CC
27badd4 
... it's just deployments of very very old caches that would be of concern here.

Given how unlikely this is in 2020, how broken they would be for other reasons, and the
prevalence of HTTPS, it seems safe to modify these statements.

Fixes #660.
@mnot mnot mentioned this issue Jan 8, 2021
Merged
@royfielding
Copy link
Member

I think the warnings can be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mnot mnot

Labels
caching has-proposal
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Even HTTP/1.0 caches now support Age and CC httpwg/http-core
2 participants
@mnot @royfielding