New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 622043 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

repair QUIC server push support which was broken by a recent refactor

Project Member Reported by ckrasic@chromium.org, Jun 21 2016

Issue description

As part of weekly merge of internal changes (https://codereview.chromium.org/1877703002), merge of internal change 
119198371 broke QUIC's server push support.

The new method  QuicSpdyStream::OnPromiseHeaderList() was not overridden in QuicChromiumClient as its predecessor OnPromiseHeadersComplete() was.  As a result, on receipt of a PUSH_PROMISE QUIC in chromium closes the connection with a error QUIC_INVALID_HEADERS_STREAM_DATA.

Unfortunately none of the existing push related unit tests caught this.  There should be a server push test(s) in quic_network_transaction_unittest.cc to prevent this from re-occurring.
 
Cleaning up the stream class hierarchy would also help to prevent this kind of problem from recurring.
Labels: Merge-Request-53

Comment 4 by dimu@chromium.org, Aug 15 2016

Labels: -Merge-Request-53 Merge-Review-53 Hotlist-Merge-Review
[Automated comment] Commit may have occurred before M53 branch point (6/30/2016), needs manual review.

Comment 5 by gov...@chromium.org, Aug 15 2016

Labels: -Merge-Review-53
M53 was branched at Chromium revision: 403382 so this change {#403040} is already in branched. No M53 merge is needed. Hence, removing "Merge-Review-53" label. Please let me know if there is any concern here. Thank you.
Any update on this?
Status: Fixed (was: Assigned)

Sign in to add a comment