docs(Fx132): HTTP/2 Server Push is now deactivated by default in most major browsers

[bsmth]

HTTP/2 Server Push is being unshipped everywhere. I'm checking everywhere we mention "Server Push" to make sure we're not recommending it anymore.

https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ

Related issues and pull requests:

• Parent issue: [HTTP] Pref off HTTP/2 push #36116
• Relnote: relnote(Fx132): HTTP/2 Server Push deactivated by default #36148

[github-actions]

Preview URLs

• /en-US/docs/Glossary/HTTP_2
• /en-US/docs/Learn/Common_questions/Web_mechanics/What_is_a_web_server
• /en-US/docs/Web/HTTP/Evolution_of_HTTP
• /en-US/docs/Web/HTTP/Headers/Save-Data
• /en-US/docs/Web/HTTP/Headers

External URLs (27)

URL: /en-US/docs/Glossary/HTTP_2
Title: HTTP/2

• https://en.wikipedia.org/wiki/HTTP/2 (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/HTTP/Headers
Title: HTTP headers

• https://datatracker.ietf.org/doc/html/rfc4229 (1 time)
• https://datatracker.ietf.org/doc/html/rfc6648 (1 time)
• https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag (1 time)
• https://en.wikipedia.org/wiki/List_of_HTTP_header_fields (1 time)
• https://firefox-source-docs.mozilla.org/devtools-user/debugger/how_to/use_a_source_map/index.html (1 time)
• https://github.com/protocol-registries/http-fields?tab=readme-ov-file (1 time)
• https://httpwg.org/specs/ (1 time)
• https://tc39.es/ecma262/ (1 time)
• https://w3c.github.io/ServiceWorker/ (1 time)
• https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html (3 times)
• https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf (1 time)
• https://www.iana.org/assignments/http-fields/http-fields.xhtml (2 times)

---

URL: /en-US/docs/Web/HTTP/Evolution_of_HTTP
Title: Evolution of HTTP

• https://caniuse.com/http3 (1 time)
• https://datatracker.ietf.org/doc/html/rfc1945 (1 time)
• https://datatracker.ietf.org/doc/html/rfc2068 (1 time)
• https://datatracker.ietf.org/doc/html/rfc2616 (1 time)
• https://datatracker.ietf.org/doc/html/rfc7230 (1 time)
• https://datatracker.ietf.org/doc/html/rfc7235 (1 time)
• https://datatracker.ietf.org/doc/html/rfc9110 (2 times)
• https://datatracker.ietf.org/doc/html/rfc9111 (1 time)
• https://datatracker.ietf.org/doc/html/rfc9112 (1 time)
• https://datatracker.ietf.org/doc/html/rfc9113 (1 time)
• https://datatracker.ietf.org/doc/html/rfc9114 (2 times)
• https://w3techs.com/technologies/details/ce-http2 (1 time)
• https://w3techs.com/technologies/details/ce-http3 (1 time)
• https://www.w3.org/People/Berners-Lee/1991/08/art-6484.txt (1 time)

(comment last updated: 2024-10-22 07:30:48)

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[hamishwillee]

Losing the information about server push good. I don't think there are other HTTP mechanisms for a server to push information to a client without their first being a request.

Though FYI it is possible for a server to include information in a response that was not requested which "somewhat" does the same thing (i.e. server provides a hint to client in any response that is unrelated to the request, triggering behaviour that looks a bit like a push). Upshot not worth mentioning here.

[bsmth]

Right, I think for the target audience of this doc, we can keep it straightforward.

[hamishwillee]

A couple of "to my taste" changes. Approving so you can merge or accept if you like.

Note that I only reviewed the changes that were made - I haven't checked if there are other mentions of server push that should be updated.

[bsmth]

Thanks, Hamish!

I haven't checked if there are other mentions of server push that should be updated.

I can't find any through code search, so I believe this is everything. I'll merge shortly 👍🏻