Received: by taz.hyperreal.com (8.8.4/V2.0) id RAA01697; Sun, 9 Feb 1997 17:09:55 -0800 (PST) Received: from scanner.worldgate.com by taz.hyperreal.com (8.8.4/V2.0) with ESMTP id RAA01648; Sun, 9 Feb 1997 17:09:49 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.7.3) with UUCP id SAA28422 for new-httpd@hyperreal.com; Sun, 9 Feb 1997 18:09:47 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id SAA13669 for ; Sun, 9 Feb 1997 18:03:52 -0700 (MST) Date: Sun, 9 Feb 1997 18:03:52 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: new-httpd@hyperreal.com Subject: Re: Lingering close: a summary In-Reply-To: <9702092238.aa29886@gonzo.ben.algroup.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com 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.