Closed
Bug 1822005
Opened 1 year ago
Closed 1 year ago
Consider to bypass client cert check for speculative connections created because of EarlyHint
Categories
(Core :: Networking, task, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
113 Branch
Tracking | Status | |
---|---|---|
firefox113 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Since we already create speculative connection for every http request anyway, maybe we can do the same for preconnect
.
Assignee | ||
Comment 1•1 year ago
•
|
||
If I understand the reason why we added these two checks in bug 910207 correctly, we want to avoid the client certificate dialog popup unexpectedly.
For the early hint case in this bug, the speculative connection is triggered by receiving 103
response from server, so maybe it's fine to bypass these two checks.
Dana, what do you think? Is there anything I missed?
Flags: needinfo?(dkeeler)
It might be, considering that the TLS handshake would have been completed at that point. That said, I would be wary of doing anything here until bug 1813618 is addressed by making client auth requests work with speculative connections.
Flags: needinfo?(dkeeler)
Assignee | ||
Comment 3•1 year ago
|
||
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b043e4385379 bypass client cert check for speculative connections created because of EarlyHint, r=manuel,necko-reviewers
Comment 5•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•