Closed
Bug 1644206
Opened 5 years ago
Closed 5 years ago
Investigate if bug 1640724 is caused by HTTP2 issue
Categories
(Core :: Networking: DNS, task, P3)
Core
Networking: DNS
Tracking
()
RESOLVED
INVALID
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(3 files)
end_stream_flag.png
No description provided.
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
Assignee | |
Comment 2•5 years ago
|
||
|
|
Assignee | |
Comment 3•5 years ago
|
||
Looking at the pcap it looks like the end stream flag is set, and all the data is there, so likely a bug in the nodejs HTTP2 implementation.
Could you also take a look at the pcap to confirm?
Thanks!
Flags: needinfo?(dd.mozilla)
|
|
Assignee | |
Comment 4•5 years ago
|
||
I think it may indeed be a nodejs issue: https://github.com/nodejs/node/issues/31309
|
||
Comment 5•5 years ago
|
||
Thank you for checking. Yes, from the log it is obvious that this is not a problem on our side.
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(dd.mozilla)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•