Updates:
Status: Fixed
Comment #6 on issue 8440 by ero...@chromium.org: TODO: Check if 1xx needs
to set message_body_length_ to 0.
http://code.google.com/p/chromium/issues/detail?id=8440
(No comment was entered for this change.)
--
You received this message because you are listed in
Updates:
Status: Started
Cc: da...@chromium.org
Comment #1 on issue 8440 by ero...@chromium.org: TODO: Check if 1xx needs
to set message_body_length_ to 0.
http://code.google.com/p/chromium/issues/detail?id=8440
Ok, so it looks like we *should* in fact be treating all 1xx the
Comment #2 on issue 8440 by ero...@chromium.org: TODO: Check if 1xx needs
to set message_body_length_ to 0.
http://code.google.com/p/chromium/issues/detail?id=8440
Justified in terms of words from RFC 2616 [Sec 10.1]
A client MUST be prepared to accept one or more 1xx status responses
Comment #5 on issue 8440 by bugdro...@chromium.org: TODO: Check if 1xx
needs to set message_body_length_ to 0.
http://code.google.com/p/chromium/issues/detail?id=8440
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=revrevision=12634
Status: Assigned
Owner: ero...@chromium.org
CC: w...@chromium.org
Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend NewHTTP
New issue 8440 by ero...@chromium.org: TODO: Check if 1xx needs to set
message_body_length_ to 0.
http://code.google.com/p/chromium/issues/detail?id=8440
From
