Mozilla is planning to disable it by default in Firefox soon, and completely remove it by ESR 140.
https://groups.google.com/a/mozilla.org ... ZsHz7TAQAJ
Will we follow? It does seem like the way HTTP/2 push is often being used makes the UX detrimental, though I can still see some use from it like instantly invalidating a browser's cache without the penalty of a roundtrip... And I really wonder why nobody has thought of using this concept to shave off RTT from HTTP 3xx responses. Instead of a back-and-forth to get to the final 200'd Location, the server could just push immediately the final response after a redirect is returned, essentially turning 3xx into a 1xx too...
It looks like HTTP/2 server push is dead in mainstream browsers
Forum rules
This General Discussion board is meant for topics that are still relevant to Pale Moon, web browsers, browser tech, UXP applications, and related, but don't have a more fitting board available.
Please stick to the relevance of this forum here, which focuses on everything around the Pale Moon project and its user community. "Random" subjects don't belong here, and should be posted in the Off-Topic board.
This General Discussion board is meant for topics that are still relevant to Pale Moon, web browsers, browser tech, UXP applications, and related, but don't have a more fitting board available.
Please stick to the relevance of this forum here, which focuses on everything around the Pale Moon project and its user community. "Random" subjects don't belong here, and should be posted in the Off-Topic board.
-
jobbautista9
- Keeps coming back
- Posts: 846
- Joined: 2020-11-03, 06:47
- Location: Philippines
- Contact:
It looks like HTTP/2 server push is dead in mainstream browsers
merry mimas
XUL add-ons developer. You can find a list of add-ons I manage at http://rw.rs/~job/software.html.
Mima avatar by 絵虎. Pixiv post: https://www.pixiv.net/en/artworks/15431817
Re: It looks like HTTP/2 server push is dead in mainstream browsers
I'm seriously wondering if it's something that makes QUIC/HTTP3 look worse (e.g. by not having it...), which means to optimize PR around it they will disable a useful feature in HTTP2...?
"A programmer is someone who solves a problem you didn't know you had, in a way you don't understand." -- unknown
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
jobbautista9
- Keeps coming back
- Posts: 846
- Joined: 2020-11-03, 06:47
- Location: Philippines
- Contact:
Re: It looks like HTTP/2 server push is dead in mainstream browsers
Btw I'm wrong about nobody thinking of pushing the final Location of a 3xx redirect, somebody certainly has as early as 2017! https://www.ctrl.blog/entry/http2-push-redirects.html
Off-topic:
I wonder how I'd be able to determine within the browser's devtools if a resource was pushed by the server. There doesn't seem any indication, and the latest Firefox's devtools don't have any indicator either. I'm therefore stuck with nghttp, but I want something as close to a real browser request-response as possible...
I wonder how I'd be able to determine within the browser's devtools if a resource was pushed by the server. There doesn't seem any indication, and the latest Firefox's devtools don't have any indicator either. I'm therefore stuck with nghttp, but I want something as close to a real browser request-response as possible...
merry mimas
XUL add-ons developer. You can find a list of add-ons I manage at http://rw.rs/~job/software.html.
Mima avatar by 絵虎. Pixiv post: https://www.pixiv.net/en/artworks/15431817