Closed
Bug 1005821
Opened 11 years ago
Closed 11 years ago
http2 GOAWAY frame sends ID field wrongly!
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: bagder, Assigned: bagder)
Details
(Whiteboard: [spdy])
Attachments
(1 file, 1 obsolete file)
1.16 KB,
patch
|
bagder
:
review+
|
Details | Diff | Splinter Review |
Http2Session::GenerateGoAway() inserts the 'mOutgoingGoAwayID' at index 7 while the comment (and the current http2 spec draft-12) says it should be at index 8.
Assignee | ||
Updated•11 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Assignee | ||
Updated•11 years ago
|
Attachment #8417254 -
Flags: review?(hurley)
Updated•11 years ago
|
Whiteboard: [spdy]
Comment on attachment 8417254 [details] [diff] [review]
suggested patch for the problem
Review of attachment 8417254 [details] [diff] [review]:
-----------------------------------------------------------------
::: netwerk/protocol/http/Http2Session.cpp
@@ +756,5 @@
> CreateFrameHeader(packet, 8, FRAME_TYPE_GOAWAY, 0, 0);
>
> // last-good-stream-id are bytes 8-11 reflecting pushes
> uint32_t goAway = PR_htonl(mOutgoingGoAwayID);
> + memcpy (packet + 8, &goAway, 4);
While you're at it, get rid of the space before the open paren, too. r=hurley with that change.
Attachment #8417254 -
Flags: review?(hurley) → review+
Assignee | ||
Comment 2•11 years ago
|
||
Fixed the space from the review
Attachment #8417254 -
Attachment is obsolete: true
Attachment #8417520 -
Flags: review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Updated•11 years ago
|
Assignee: nobody → daniel
Comment 3•11 years ago
|
||
Please provide a Try link. Suggestions for what to run if you haven't yet can be found here:
https://wiki.mozilla.org/Sheriffing/How:To:Recommended_Try_Practices
Keywords: checkin-needed
Daniel - just do an xpcshell try run to hit the http/2 unit tests. No other tests will be using http/2 at all, unless someone is doing something very weird we don't know about (hint - they're not. none of the protocol updates have broken anything.)
Assignee | ||
Comment 5•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 6•11 years ago
|
||
Keywords: checkin-needed
Comment 7•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in
before you can comment on or make changes to this bug.
Description
•