Open
Bug 1646701
Opened 4 years ago
Updated 2 years ago
HttpTransaction may read data but return 0 bytes read
Categories
(Core :: Networking: HTTP, task, P3)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: dragana, Unassigned)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 obsolete file)
Here a transaction reads data from a pipe.
After reading the header part of data it actually moves data in the buffer, so the buffer becomes smaller (here).
So if there are only headers in the stream, the transaction will return the smaller buffer back to the pipe and also 0 bytes read.
The pipe will be happy with this, but some http2 and http3 code (maybe also the http1.1 code paths) rely on the "bytes read", i.e. if it is >0 the transaction has read some data if it is 0 it did not read any data. In the case above the transaction has read headers but it has return 0 bytes.
Reporter | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Priority: -- → P2
Whiteboard: [necko-triaged]
Reporter | ||
Comment 2•3 years ago
|
||
This is how this has always worked. This is not a defect it is intended behavior. We may wan to change it at some point.
Assignee: dd.mozilla → nobody
Severity: S4 → N/A
Type: defect → task
Priority: P2 → P3
Updated•2 years ago
|
Attachment #9157689 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•