W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1996

Re: status code 100 (continue)

From: Koen Holtman <koen@win.tue.nl>
Date: Wed, 6 Nov 1996 23:22:45 +0100 (MET)
Message-Id: <199611062222.XAA21635@wsooti04.win.tue.nl>
To: rlgray@raleigh.ibm.com
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1881
>The way I read section 8.2 (message transmission requirements) is: 
>IF ((client is 1.1) AND (NOT connection:close)) then I MUST send 
>status 100 or an error. 

The connection:close conjunct does not come into it.  It is 

IF (client is 1.1) then ....

but only for responses to certain methods.  In the text of 14.10:

|HTTP/1.1 defines the "close" connection option for the sender to signal
|that the connection will be closed after completion of the response.

`completion of the response' does not mean completion of the 100
response, but completion of the entire HTTP/1.1 response, possibly
consisting of a 100 followed by something else.  A 100 response is an
`interim response' only.

>Will clients get confused receiving 100 even if connection:close? 

Not if they are correctly implemented 1.1 clients.

>Do I *really* have to send a Date header? 

Yes, but not in the preliminary 100 response part.  The spec wants you
to send:

 100 Continue

 200 OK
 Date: Tue, 15 Nov 1994 08:12:31 GMT


and the whole thing should be seen as a single HTTP response.  I
notice that the spec is not very clear on this, there should probably
be more explanatory text in 10.1.

>And, (once again) what is the rationale for the 100 response? 
>It seems unnecessary and wasteful; what am I missing here? 

I never heard a rationale that convinced me we needed it.

>Thank You, 
>Richard L. Gray

Received on Wednesday, 6 November 1996 14:30:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC