Rename Cache header to Cache-Status #777
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cache-Status seems to better describe the information this header carries
and is potentially less confusing. It also seems more consistent with other
Cache-related headers (e.g. Cache-Control).
FWIW, some variants of *-Cache-Control are also somewhat popular in the
wild, e.g. the NGINX caching guide [0] uses X-Cache-Status and Cloudflare
uses CF-Cache-Control (though I'm not sure popularity matters much, since
either way servers will need to be updated).
[0] https://www.nginx.com/blog/nginx-caching-guide/
@mnot As proposed a while ago on the mailing list https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0318.html Happy to discuss this more in Prague.