Re: I-D Action: draft-ietf-httpbis-http2-09.txt

On 4 December 2013 22:37, Ilari Liusvaara <> wrote:
>> The server can send a final status code at any time, with HTTP/1 or HTTP/2.
>> The client can choose whether to start sending the body or hold back, both
>> with HTTP/1 and HTTP/2.
> Well, final status codes mid-body are somewhat unlikely, and would likely
> be caused by problems in the body itself (or server bugs).
> Without positive acknowledgement one needs to timeout on success case
> before one can send unbuffered part.

Yes, this is correct.  Losing 100 means that you don't get an
acknowledgement.  But why would you hold back?  The server has a
receive window that protects it from unwanted request bodies; just
send.  If it doesn't want it, you will get a response or a stream

Note that a server that wants 100 continue-equivalent behaviour can
set an initial window size for stream of zero.

The only drawback is for clients that want to save bytes.  Those
clients can implement a timeout of ~1RTT if they want to avoid that
cost.  That's the only downside from removing 1xx support.  There's a
lot of upside though.

Received on Thursday, 5 December 2013 18:11:49 UTC