Update caching based on RFC9111

[Jxck]

Summary

It's been a long since #10027 but it's the rest of task updating caching section align with RFC9111 (new RFC not published yet).

Motivation

updating http caching section align with cache-control section and new RFC9111

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control

Related issues

#8668

Metadata

• Adds a new document
• Rewrites (or significantly expands) a document
• Fixes a typo, bug, or other error

[Jxck]

hope @sideshowbarker fixing my writing and @mnot reviewing technical details.

[github-actions]

Preview URLs

• https://pr16009.content.dev.mdn.mozit.cloud/en-US/docs/Web/HTTP/Caching

Flaws

None! 🎉

External URLs

URL: /en-US/docs/Web/HTTP/Caching
Title: HTTP caching
on GitHub

• https://blog.chromium.org/2017/01/reload-reloaded-faster-and-leaner-page_26.html (1 time) (Note! This may be a new URL 👀)
• https://datatracker.ietf.org/doc/html/RFC9111 (1 time) (Note! This may be a new URL 👀)
• https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cache (1 time) (Note! This may be a new URL 👀)
• https://datatracker.ietf.org/doc/html/rfc9204 (1 time) (Note! This may be a new URL 👀)
• https://docs.microsoft.com/en-us/troubleshoot/developer/browsers/connectivity-navigation/how-to-prevent-caching (1 time) (Note! This may be a new URL 👀)
• https://fetch.spec.whatwg.org/ (2 times) (Note! This may be a new URL 👀)
• https://groups.google.com/a/mozilla.org/g/dev-platform/c/I939w1yrTp4 (1 time) (Note! This may be a new URL 👀)
• https://www.mnot.net/cache_docs (1 time) (Note! This may be a new URL 👀)

(this comment was updated 2022-05-16 09:35:08.208811)

[sideshowbarker]

Amazingly great work as usual

[Jxck]

@sideshowbarker thanks for quic response. But I think it's better reviewed by @mnot too before merging since it's changes old contents a lot and affects caching recommendation widely.

[sideshowbarker]

@sideshowbarker thanks for quic response. But I think it's better reviewed by @mnot too before merging since it's changes old contents a lot and affects caching recommendation widely.

There's no guarantee that Mark is necessarily going to have time to review it. And anyway, it can still be reviewed post-commit. Any changes can be made in a follow-up PR.