3 ms·
> This means that if webservers and websites use push and don't test in Firefox, this feature can potentially cause websites to stop working only in Firefox Th
by rrr_oh_man 2y ago
> This means that if webservers and websites use push and don't test in Firefox, this feature can potentially cause websites to stop working only in Firefox
That is one reading of the situation.
The other would be:
All other browsers reject HTTP/2 Push & gracefully ignore it, but Firefox majorly trips up in edge cases.
(quote: «It seems that Firefox is resetting the connection because it encounters an uppercase character in the header names»).
- jorams 2y agoYour reading doesn't really make sense. Other browsers don't implement the specification. Firefox does. The specification is very explicit about how this violation should be treated. Those webservers and websites have a broken implementation. Had they tested with any spec compliant client they would have noticed it being broken.
- deleted 2y ago[deleted]
- chrismorgan 2y agoIt could just as easily have gone the other way: a new spec implemented only in one browser (typically Chrome, as it most frequently ships things first, often incomplete) and, badly implemented by a server, causing such a problem.
- swiftcoder 2y agoI mean, that's pretty much how we got HTTP/2 Push as a standard in the first place, so it's somewhat fitting we lose it the same way.
- rdsubhas 2y agoThey make it clear in their post: > Firefox has continued supporting HTTP/2 push as this wasn't too large of an effort until recently. > However in the past few months we've encountered some webcompat bugs only affecting Firefox through HTTP/2 push They are clearly saying that recently there has been bug report, and this blog post is to do exactly what you mentioned as other browsers do: reject H2 push and gracefully ignore it. There does not appear to be any hiding here.