httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@gonzo.ben.algroup.co.uk>
Subject Re: Lingering close: a summary
Date Mon, 10 Feb 1997 09:23:33 GMT
Marc Slemko wrote:
> 
> On Sun, 9 Feb 1997, Ben Laurie wrote:
> 
> > Marc Slemko wrote:
> > > 
> > >    Upon receiving a method subject to these requirements from an
> > >    HTTP/1.1 (or later) client, an HTTP/1.1 (or later) server MUST either
> > >    respond with 100 (Continue) status and continue to read from the
> > >    input stream, or respond with an error status. If it responds with an
> > >    error status, it MAY close the transport (TCP) connection or it MAY
> > >    continue to read and discard the rest of the request. It MUST NOT
> > >    perform the requested method if it returns an error status.
> > > 
> > >    Clients SHOULD remember the version number of at least the most
> > >    recently used server; if an HTTP/1.1 client has seen an HTTP/1.1 or
> > >    later response from the server, and it sees the connection close
> > >    before receiving any status from the server, the client SHOULD retry
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> The response will likely be truncated in the middle, hence the above
> does not apply since it has recieved status.  

Hang about. The client can tell when the status is complete (it is terminated
with a blank line). So I can't agree with this.

Cheers,

Ben.

-- 
Ben Laurie                Phone: +44 (181) 994 6435  Email: ben@algroup.co.uk
Freelance Consultant and  Fax:   +44 (181) 994 6472
Technical Director        URL: http://www.algroup.co.uk/Apache-SSL
A.L. Digital Ltd,         Apache Group member (http://www.apache.org)
London, England.          Apache-SSL author

Mime
View raw message