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

Re: Expect: 100-continue and proxies

From: Jamie Lokier <jamie@shareable.org>
Date: Sun, 21 Feb 2010 19:28:30 +0000
To: Joe Orton <joe@manyfish.co.uk>
Cc: ietf-http-wg@w3.org
Message-ID: <20100221192830.GA1086@shareable.org>
Joe Orton wrote:
> 2616 s8.2.3 first bullet of the requirements for proxies has a MUST 
> requirement that a proxy forwards the Expect header to the next hop.
> 
> Apache httpd complies with this (whether by design or by accident, I'm 
> not sure), though it makes little sense: the proxy is written to read 
> and forward the entire request body without waiting for an interim 
> response from the server.

The proxy doesn't have to wait, because the client which sent Expect
will not send a request body for the proxy to forward, until the
timeout heuristic triggers.  There is no need for another delay from
the proxy.

> Why is a MUST condition for the server to forward the 100-continue 
> expectation appropriate, regardless of how a proxy handles the client's 
> request body?

Because if it does not, there will be no 100 Continue sent to the
client, and the request body will be unnecessarily delayed.

-- Jamie
Received on Sunday, 21 February 2010 19:28:58 GMT

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