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

Re: #467: Expect: 100-continue and "final" status codes

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 28 May 2013 08:22:52 +0200
To: Mark Nottingham <mnot@mnot.net>
Cc: Zhong Yu <zhong.j.yu@gmail.com>, Ken Murchison <murch@andrew.cmu.edu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20130528062252.GA30665@1wt.eu>
Hi Mark,

On Tue, May 28, 2013 at 04:03:36PM +1000, Mark Nottingham wrote:
> There aren't any new requirements in there; all of this text is only
> describing semantics and giving implementation advice. What if we modify the
> text slightly, e.g.,
> 
> """
> 100-continue
> 
> * The request includes a payload body and, after sending the request header
> section, the client will wait before some (possibly unbounded) period of time
> before sending it, to give the server an opportunity to reject the request
> with a final status code. The server can shorten the wait time by sending a
> 100 (Continue) response.
> """

I personally think the "possibly unbounded" part solves the issue. However,
we should ass "or a final status code" at the end of the last sentence.

Best regards,
Willy
Received on Tuesday, 28 May 2013 06:23:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC