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

Re: p2: Expect: 100-continue and "final" status codes

From: Ken Murchison <murch@andrew.cmu.edu>
Date: Tue, 23 Apr 2013 09:39:29 -0400
Message-ID: <51768F11.2070707@andrew.cmu.edu>
To: ietf-http-wg@w3.org, Mark Nottingham <mnot@mnot.net>
On Tue, 23 Apr 2013 17:22:37 +1000, Mark Nottingham wrote:
> p2 5.1.1.1 explains the semantics of 100-continue: "If the origin 
> server responds with a final status code, it must not have performed 
> the request method and may either close the connection or continue to 
> read and discard the rest of the request."  
>
> In my (admittedly quick) testing, pretty much nobody does this, at 
> least by default; i.e., if I send a GET to a server with Expect: 
> 100-continue, it's going to give me a 200 or 30x, not a 417. Sure, 
> they might send 417 for a request with a body, but as written pretty 
> much no one is conformant.
This bring up a question:  For those methods where a body isn't 
currently defined and/or typically isn't expected, is a server supposed 
to distinguish between cases when the request includes a body vs the 
request includes Expect:100-continue?  Are the correct responses 415 and 
417 respectively?

And what about TRACE?  Is 400 the correct response in both cases?

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
Received on Tuesday, 23 April 2013 13:39:58 UTC

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