Set network.http.http2.send_NO_RFC7540_PRI to false
Categories
(Core :: Networking: HTTP, task, P1)
Tracking
()
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(3 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr128+
|
Details | Review |
There seem to be some servers that close the TLS connection when they encounter this.
Setting to false matches Chrome.
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D228433
Updated•1 year ago
|
Comment 3•1 year ago
|
||
beta Uplift Approval Request
- User impact if declined: Some webservers might close the connection
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See bug 1928600
- Risk associated with taking this patch: low
- Explanation of risk level: This patch just makes it so we don't send the SETTINGS_NO_RFC7540_PRIORITIES option. We will then match Chrome. The only risk is that servers might mistakenly use HTTP/2 stream weights for prioritization, instead of the priority header, but the webcompat risk is low considering Chrome is doing the same thing.
- String changes made/needed: none
- Is Android affected?: yes
| Assignee | ||
Comment 4•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D228433
Updated•1 year ago
|
Comment 5•1 year ago
|
||
release Uplift Approval Request
- User impact if declined: Some webservers might close the connection prematurely leading to a failure to load the page.
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See bug 1928600
- Risk associated with taking this patch: low
- Explanation of risk level: This patch just makes it so we don't send the SETTINGS_NO_RFC7540_PRIORITIES option. We will then match Chrome. The only risk is that servers might mistakenly use HTTP/2 stream weights for prioritization, instead of the priority header, but the webcompat risk is low considering Chrome is doing the same thing.
- String changes made/needed: none
- Is Android affected?: yes
| Assignee | ||
Comment 6•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D228433
Updated•1 year ago
|
Comment 7•1 year ago
|
||
esr128 Uplift Approval Request
- User impact if declined: Some webservers might close the connection prematurely leading to a failure to load the page.
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See bug 1928600
- Risk associated with taking this patch: low
- Explanation of risk level: This patch just makes it so we don't send the SETTINGS_NO_RFC7540_PRIORITIES option. We will then match Chrome. The only risk is that servers might mistakenly use HTTP/2 stream weights for prioritization, instead of the priority header, but the webcompat risk is low considering Chrome is doing the same thing.
- String changes made/needed: none
- Is Android affected?: yes
Updated•1 year ago
|
Comment 10•1 year ago
|
||
| uplift | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 11•1 year ago
•
|
||
Reproduced the issue on Windows 10x64 with Firefox 133.0b6 by opening https://spacedock.info/. A Secure connection failed error is displayed and the network.http.http2.send_NO_RFC7540_PRI pref is set to true.
The issue is verified fixed with Firefox 134.0a1 (2024-11-11) and 133.0b7 from comment 10 on Windows 10x64, macOS 12 and Ubuntu 24. The https://spacedock.info/ is successfully loaded and network.http.http2.send_NO_RFC7540_PRI is set to false.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 12•1 year ago
|
||
| uplift | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 13•1 year ago
|
||
The issue is verified fixed with Firefox 128.5.0esr on Windows 10x64, macOS 12 and Ubuntu 24. The https://spacedock.info/ is successfully loaded and network.http.http2.send_NO_RFC7540_PRI is set to false.
Description
•