Open Bug 1994321 Opened 2 months ago Updated 2 months ago

Decide fallback strategy when 0-RTT is involved

Categories

(Core :: Networking: HTTP, defect, P2)

Product:
Core
Component:
Networking: HTTP
Type:
defect

Tracking

()

People

(Reporter: kershaw, Unassigned)

References

(Blocks 1 open bug)

Details

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

Currently, when 0-RTT is used, there’s no fallback: if a resumption token is available, we assume the connection is usable. However, the network may have changed and the resumed HTTP/3 connection could be blocked. In that case, we should detect the failure quickly and fall back to HTTP/2.

Whiteboard: [necko-triaged]
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-queue]
You need to log in before you can comment on or make changes to this bug.