W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2010

Re: 100 Continue and Expects

From: David Morris <dwm@xpasc.com>
Date: Sat, 27 Mar 2010 12:33:46 -0700 (PDT)
To: Greg Wilkins <gregw@webtide.com>
cc: ietf-http-wg@w3.org
Message-ID: <Pine.LNX.4.64.1003271230550.13635@egate.xpasc.com>



On Sat, 27 Mar 2010, Greg Wilkins wrote:

> I'd like to wake up the discussion about 100 Continues in the specification.
> 
> In my experience with the Jetty server, one of the main users of Expect
> continues is .net clients doing webservices.   Unfortunately there appears
> to be a some clients that although they send expect 100 continues, they
> always send the body regardless if the server has sent 100 continues
> or not.
> 
...
> 
> So it would be great if the spec could give guidance to
> tell servers what to do with data that is received
> before any response is sent to an expect 100 continues.
> 
> Perhaps something like:
> 
>     An origin server MUST read the request body if it has
>         already received some or all of the request body for the
>         corresponding request before sending any response

I don't think so ... the server MUST be prepared to deal with the
unexpected input ... could be a connection reset ... I don't think
it is our place to dictate error handling. 

A new MUST also isn't possible as that would change the protocol.
Received on Saturday, 27 March 2010 19:34:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:17 GMT