Closed Bug 1867006 Opened 11 months ago Closed 11 months ago

Disable HTTP2 websockets until we can resolve proxy issues.

Categories

(Core :: Networking: WebSockets, defect, P1)

defect

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox121 --- fixed
firefox122 --- fixed

People

(Reporter: valentin, Assigned: kershaw)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged][necko-priority-queue])

Attachments

(2 files, 1 obsolete file)

It seems using HTTP2 websockets with a HTTP2 proxy can sometimes cause WS to not work, or even crashes.
We should disable this until we can fix it and get CI to test this exact scenario to avoid regressions.

Attachment #9365824 - Attachment is obsolete: true
Assignee: moz.valentin → kershaw
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f5a650ef4de4 Disable HTTP2 websockets until we can resolve proxy issues. r=necko-reviewers,valentin

Backed out for causing failure on test_websocket_http2.html

Backout link

Push with failures

Failure log

Flags: needinfo?(kershaw)
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/74f50e5d5557 Disable HTTP2 websockets until we can resolve proxy issues. r=necko-reviewers,valentin
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch

Let's uplift this to beta.

Flags: needinfo?(kershaw)
Attachment #9366254 - Flags: approval-mozilla-beta?

Uplift Approval Request

  • Risk associated with taking this patch: No risk. This patch is basically a pref flip.
  • String changes made/needed: N/A
  • Needs manual QE test: no
  • User impact if declined: Possible crash
  • Fix verified in Nightly: yes
  • Steps to reproduce for manual QE testing: N/A
  • Explanation of risk level: Low
  • Is Android affected?: yes
  • Code covered by automated testing: yes
Flags: needinfo?(kershaw)

Comment on attachment 9366254 [details]
Bug 1867006 - Disable HTTP2 websockets until we can resolve proxy issues. r=#necko

Approved for 121.0b6.

Attachment #9366254 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Regressions: 1869343

Is it possible to backport this fix to Firefox ESR? (or backport the patch in bug 1848013, whatever is easier or more relevant)
My team meets lots of Firefox users who cannot use a service relying on Websocket exclusively because of what has been reported in bug 1848013 (their websocket connections pass through a squid Proxy). It really penalizes them.

Flags: needinfo?(kershaw)

I've requested to uplift the patch in bug 1848013 to ESR.

Flags: needinfo?(kershaw)

Thank you Kershaw!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: