Closed
Bug 1822391
Opened 2 years ago
Closed 2 years ago
Problems when receiving STOP_SENDING in WebTransport code
Categories
(Core :: Networking: HTTP, defect, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
DUPLICATE
of bug 1824243
People
(Reporter: jesup, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
1.55 MB,
text/plain
|
Details |
The STOP_SENDING tests in the streams-close wpt test timeout. Running just the next-to-last test (the first that causes a timeout), it hangs after writing to the stream (which should cause the server to send STOP_SENDING). The test expects that the writer will be closed with a WebTransportError, which doesn't happen (or it happens after timeout).
Logs attached. It's possible something simply isn't hooked up; though there are no logs from the stream/session proxies when this happens
|
||
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
|
Reporter | |
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•