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

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 666383

Blocking:
issue 671310



Sign in to add a comment
link

Issue 662197: Ignore 1xx (informational) HTTP status codes in HTTP/2.

Reported by mmenke@chromium.org, Nov 3 2016 Project Member

Issue description

With a status 1xx response, the client is supposed to keep on reading headers until it gets a set of headers with a non-1xx response.  This works for HTTP, but not HTTP2, where we treat the second set of headers as a trailer, and return an error after that, as we don't expect body data after the trailers.  I suspect we do the same for QUIC, but haven't verified it.

Here's a sample H2 site that Chrome fails to load (Edge apparently handles it, haven't tested it):  https://nghttp2.org/?103-eh

There's some discussion of using a 103 status code to return link rel hints.  Regardless of whether that pans out or not, should we support 100 responses over HTTP2/QUIC?
 

Comment 1 by mmenke@chromium.org, Nov 14 2016

bnc/rch:  Any thoughts on this?  Not the highest priority issue, but if 100 responses are allowed under H2/QUIC, seems like we should be supporting them.

Comment 2 by rch@chromium.org, Nov 14 2016

Yeah this is probably something which should be done eventually. Not sure how important it is thought.

Comment 3 by mmenke@chromium.org, Nov 14 2016

Probably pretty low importance, unless other browsers are doing / start doing something that encourages HTTP/2 sites to use 100 status codes.

Comment 4 by patrick....@gmail.com, Nov 15 2016

firefox handles this correctly along with edge. The 103 change is being seriously considered as standards track, would hate to see that held back by a chrome bug.

Comment 5 by b...@chromium.org, Nov 15 2016

Cc: -b...@chromium.org
Labels: -Pri-3 M-57 Pri-2
Owner: b...@chromium.org
Status: Started (was: Untriaged)
Re #4: Thank you for the heads up.  Bumping priority accordingly.

Comment 6 by b...@chromium.org, Nov 17 2016

Blockedon: 666383
Summary: Add support for 1xx (informational) HTTP status codes in HTTP/2 (was: Chrome doesn't support HTTP 100 responses over HTTP2: Should it?)

Comment 7 by b...@chromium.org, Nov 30 2016

 Issue 669820  has been merged into this issue.

Comment 8 by igrigo...@chromium.org, Nov 30 2016

Cc: igrigo...@chromium.org

Comment 9 by b...@chromium.org, Dec 5 2016

Blocking: 671310

Comment 10 by b...@chromium.org, Dec 5 2016

Summary: Ignore 1xx (informational) HTTP status codes in HTTP/2. (was: Add support for 1xx (informational) HTTP status codes in HTTP/2)
Since this issue is focused on ignoring 1xx headers vs choking on them (and not so much on actually acting on 103 Early Hints), I am changing title of this issue to reflect that, and filing issue 671310, with lower priority, for acting on 103 Early Hints.

Comment 13 by b...@chromium.org, Dec 6 2016

Status: Fixed (was: Started)

Sign in to add a comment