Content deleted Content added
m I corrected minor errors |
remove hat notes (issues seem addressed since the given dates) |
||
| (3 intermediate revisions by 3 users not shown) | |||
Line 1:
{{Short description|Outdated web optimization protocol}}
{{use dmy dates|date=April 2022|cs1-dates=y}}
'''HTTP/2 Server Push''' is an optional<ref>{{Cite journal |date=May 2015 |title=Hypertext Transfer Protocol Version 2 (HTTP/2) |doi=10.17487/RFC7540 |url=https://www.rfc-editor.org/rfc/rfc7540 |quote=A client can request that server push be disabled|last1=Belshe |first1=M. |last2=Peon |first2=R. |last3=Thomson |first3=M. |editor-first1=M |editor-last1=Thomson |doi-access=free }}</ref> feature of the [[HTTP/2]] and [[HTTP/3]] [[Communication protocol|network protocols]] that allows [[Server-side|servers]] to send resources to a [[Client–server model|client]] before the client requests them. Server Push is a performance technique aimed at reducing latency by sending resources to a client preemptively before it knows they will be needed.<ref>{{Cite web |last=Staff |first=Ars |date=2015-02-18 |title=HTTP/2 finished, coming to browsers within weeks |url=https://arstechnica.com/information-technology/2015/02/http2-finished-coming-to-browsers-within-weeks/ |access-date=2023-01-12 |website=Ars Technica |language=en-us}}</ref> In practice, Server Push frequently results in wasted bandwidth because the server rarely knows which resources are already loaded by the client and transmits the same resource multiple times, resulting in slowdowns if the resources being pushed compete for bandwidth with resources that were requested.<ref name=":0">{{Cite web |date=2020-11-11 |title=Intent to Remove: HTTP/2 and gQUIC server push |url=https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1 |url-status=live |archive-url=https://web.archive.org/web/20211128080039/https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1 |archive-date=2021-11-28 |access-date=2022-04-12 |website=[[Google Groups]] |language=en}}</ref>
Line 18 ⟶ 14:
In October 2022, Google announced their intent to remove Server Push from Google Chrome, citing the poor performance of the extension in practice, lack of use and better alternatives. Chrome 106 became the first release disabling Server Push by default.<ref name=":2">{{Cite web |date=2022-08-18 |title=Removing HTTP/2 Server Push from Chrome |url=https://developer.chrome.com/blog/removing-push/ |access-date=2023-07-30 |website=Chrome Developers |language=en}}</ref>
On October 29, 2024, [[Mozilla Corporation|Mozilla]] released [[Firefox]] 132, which removed HTTP/2 Server Push support due to "compatibility issues with various sites".<ref>{{Cite web |title=Firefox 132.0, See All New Features, Updates and Fixes |url=https://www.mozilla.org/en-US/firefox/132.0/releasenotes/ |access-date=2024-10-29 |website=Mozilla |language=en}}</ref>
== Protocol ==
Line 49 ⟶ 47:
|Client
|?
|131.0 Beta 9<ref>{{Cite web |title=Intent to unship: HTTP/2 Push |url=https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ |access-date=2024-09-06 |website=groups.google.com}}</ref><ref>{{Cite web |title=Firefox Beta 132.0beta, See All New Features, Updates and Fixes |url=https://www.mozilla.org/en-US/firefox/132.0beta/releasenotes/?utm_source=firefox-browser&utm_medium=firefox-desktop&utm_campaign=about-dialog |access-date=2024-10-01 |website=Mozilla |language=en}}</ref>
|}
| |||