Closed Bug 1759292 Opened 7 months ago Closed 4 months ago

Allow HTTP/3 to work even after Shift-reload

Categories

(Core :: Networking: HTTP, enhancement, P3)

Firefox 100
enhancement

Tracking

()

RESOLVED FIXED
103 Branch
Tracking Status
firefox100 --- wontfix
firefox103 --- fixed

People

(Reporter: d4v1d_4n0, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Keywords: parity-chrome, Whiteboard: [necko-triaged])

Attachments

(1 file)

In Chromium browsers, the use of HTTP/3 continues even after Shift-reloads (a.k.a forced refresh) or Ctrl/Control+F5

Unfortunately Firefox clears all alt-svc mappings and will not even use HTTP/3 again after shift reload, and then even normal reload does not work.

I guess Firefox needs to change this behaviour because HTTP/3 will no longer be a draft in the future and alt-svc mappings need to be consistent.

Blocks: QUIC
Keywords: parity-chrome

Dragana, what do you think?
Thanks.

Flags: needinfo?(dd.mozilla)

I knew about this bug. I have a patch already, I did don't have time to submit it.

Assignee: nobody → dd.mozilla
Severity: -- → N/A
Status: NEW → ASSIGNED
Flags: needinfo?(dd.mozilla)
Priority: -- → P3
Whiteboard: [necko-triaged]

AltSvc mapping is cleared and if we do not clear the coalescing mapping it may happen that AltSvc cannot be validated because an alternative connection using DNS mapping already exists.

We clear AltSvc mapping because hard-refresh is a sign of a problem loading a page and we should start fresh, that should mean for the coalescing hashmap as well.

Pushed by ddamjanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a58bd57bd6b5
Clear the coalescing key mapping on hard-refresh r=necko-reviewers,kershaw
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in before you can comment on or make changes to this bug.