Closed Bug 1930122 Opened 1 year ago Closed 1 year ago

Set network.http.http2.send_NO_RFC7540_PRI to false

Categories

(Core :: Networking: HTTP, task, P1)

task

Tracking

()

VERIFIED FIXED
134 Branch
Tracking Status
firefox-esr128 --- verified
firefox133 --- verified
firefox134 --- verified

People

(Reporter: valentin, Assigned: valentin)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(3 files, 1 obsolete file)

There seem to be some servers that close the TLS connection when they encounter this.
Setting to false matches Chrome.

Attachment #9436384 - Flags: approval-mozilla-beta?

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
Flags: qe-verify+
Attachment #9436385 - Flags: approval-mozilla-release?

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
Attachment #9436386 - Flags: approval-mozilla-esr128?

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
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/80c3d05c3f49 Set network.http.http2.send_NO_RFC7540_PRI to false r=necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
Attachment #9436384 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-triaged]

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.

Has STR: --- → yes
QA Whiteboard: [qa-triaged]
Flags: qe-verify+
Attachment #9436386 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
Attachment #9436385 - Flags: approval-mozilla-release? → approval-mozilla-release-
Blocks: 1928600
Attachment #9436385 - Attachment is obsolete: true

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.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: