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

Re: Deploying new expectation-extensions

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Sun, 06 Apr 2008 18:21:38 +0200
To: Jamie Lokier <jamie@shareable.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, google-gears-eng@googlegroups.com
Message-Id: <1207498898.21800.61.camel@HenrikLaptop>

sön 2008-04-06 klockan 15:22 +0100 skrev Jamie Lokier:
> The client can always send the request entity, because if there's a
> HTTP/1.0 proxy in the chain, the client won't receive 100 Continue, so
> HTTP/1.1 clients have an unspecified short timeout and send it anyway.

Thats only if 100 Continue has never been seen from the requested
server... If the client has seen a 100 Continue ever from the requested
server it should wait indefinitely.

Hmm.. when reading 2616 one more on the use of 100 Continue it's pretty
clear 2616 should have been an 1.2 version bump from 2068 to clean up
this mess... some heavy heuristics involved there to tell 2068 1.1 apart
from 2616 1.1, even with a MAY requirement overriding a SHOULD NOT...

> The 100 Continue is a hint to continue immediately, instead of after a
> short timeout.  The idea is if the server sends an error response
> (quickly), the client can abort the request and close the connection
> without transmitting any part of the entity.

That's one aspect of it. But there is more aspects of 100 Continue, and
more conditions governing it's use.

Regards
Henrik
Received on Sunday, 6 April 2008 16:23:41 GMT

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