www.mapbusinessonline.com - The page refuses to load - h2 priority
Categories
(Core :: Networking: HTTP, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | fixed |
firefox128 | --- | fixed |
firefox129 | --- | fixed |
firefox130 | --- | fixed |
People
(Reporter: rbucata, Unassigned)
References
(Regression, )
Details
(Keywords: regression, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs][necko-triaged][necko-priority-queue])
Attachments
(1 file)
276.45 KB,
application/x-pcapng
|
Details |
Environment:
Operating system: Windows 10
Firefox version: Firefox 128.0
Steps to reproduce:
- Navigate to: https://www.mapbusinessonline.com
- Observe
Expected Behavior:
The page loads
Actual Behavior:
Browser does nothing
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, and Firefox Release
- Does not reproduce in Chrome
- Turning off
network.http.http2.allow-pus
solves the issue
Created from https://github.com/webcompat/web-bugs/issues/139430
Reporter | ||
Updated•4 months ago
|
Comment 1•4 months ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=750a9d68013bf86f5d1e16ddc95cce396fffd4a2&tochange=deedf27980767ec044741273bc0c9ad212bc4e1d
Updated•4 months ago
|
Comment 2•4 months ago
|
||
Kershaw, can you take a look?
Updated•4 months ago
|
Comment 3•4 months ago
|
||
It looks h2 server push is enabled by default, network.http.http2.allow-push
, but this doesn't play well with Extensible Prioritization Scheme for HTTP/2 in bug 1865040.
Updated•4 months ago
|
Comment 4•4 months ago
|
||
This bug is caused by bug 1865040, as we disabled sending the HTTP/2 dependency tree to the server. According to RFC 9218, Firefox is not doing anything wrong, but apparently, some servers are not yet compliant with RFC 9218.
I'll dup this bug with bug 1909666 and provide a patch in that bug.
Updated•4 months ago
|
Updated•3 months ago
|
Comment 5•1 month ago
|
||
PCAP for historical purposes.
It turns out the webserver would reset the TCP connection upon receiving a PRIORITY_UPDATE frame for the pushed stream.
Description
•