Open
Bug 1914425
Opened 1 year ago
Updated 8 months ago
HTTP/2: graceful handling of change of network during connection establishment
Categories
(Core :: Networking: HTTP, enhancement, P3)
Core
Networking: HTTP
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox131 | --- | affected |
People
(Reporter: acreskey, Unassigned)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [necko-triaged])
To my understanding, HTTP/3 allows seamless connection migration via QUIC, but HTTP/2, relying on TCP, doesn't support this due to the need to reset connections when the network changes.
While seamless migration isn't possible in HTTP/2, we could potentially improve how a change of network is handled during connection establishment.
Switching networks mid-connection can happen frequently for mobile users.
Bug 1706377 made progress in this space, but I understand that the changes are mostly for VPN users.
| Reporter | ||
Updated•1 year ago
|
Blocks: perf-android
| Reporter | ||
Comment 1•8 months ago
|
||
Removing from current project scope because this isn't directly actionable without specific test cases.
No longer blocks: 1951764
You need to log in
before you can comment on or make changes to this bug.
Description
•