Closed
Bug 1812617
Opened 2 years ago
Closed 2 years ago
Investigate why we sometimes (with rr for example) don't appear to send close_info data
Categories
(Core :: Networking: HTTP, defect, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jesup, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Running the close wpt test with rr often/always returns {} from the server when querying for the close_info from the previous connection; this seems like some sort of race perhaps blocking us from sending the close properly before killing the channel
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
Reporter | ||
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•