W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

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

From: Michael Sweet <msweet@apple.com>
Date: Thu, 05 Dec 2013 11:04:07 -0500
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <2B958182-72C3-4C41-84FD-D8B7E1BA7336@apple.com>
To: Mark Nottingham <mnot@mnot.net>

On Dec 5, 2013, at 1:09 AM, Mark Nottingham <mnot@mnot.net> wrote:
>> ...
>> waiting, and with any sort of faster link, those buffers are going
>> to run out, forcing transfer pause).
> 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. 

Keep in mind that for POST and PUT, servers should not send successful status codes (2xx) until the client has provided all of the message body for the request. Among other things, doing so prevents the server from accurately reporting status and prevents pipelining from working at all.  And it does *bad* things with many clients/proxies that think a 200 OK response means they can stop sending data...

Michael Sweet, Senior Printing System Engineer, PWG Chair
Received on Thursday, 5 December 2013 16:04:39 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:39 UTC