W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997

Re: HTTP 1.1 Issue: When To Close Connections

From: Dave Kristol <dmk@bell-labs.com>
Date: Fri, 23 May 1997 17:21:40 -0400
Message-Id: <33860A64.60E33853@bell-labs.com>
To: "John C. Mallery" <jcma@ai.mit.edu>
Cc: http-wg@cuckoo.hpl.hp.com
John C. Mallery wrote:
> 
> HTTP 1.1 could use a comprehensive table indicating whether a
> 1.1 server should close the connection or keep it open when various
> error states occur, in particular, 400 and 500 series codes.
> 
> Particularly important is when a 1.1 server tries to keep open a
> connection to a 1.0 client with keep alive.
> 
> The short story for 1.0 is to always close for 400 and 500 series codes.

Except for 401 Unauthorized and 407 Proxy Authentication Required?

> 
> For 1.1, the spec needs requirements for both server and client to assure
> synchronization whenever connections remain open.
> 
> Implementos will benefit from a clear statement of these issues.

I agree a list would be helpful.  However, it's awkward to have advice
about an unofficial 1.0 extension (Connection: keepalive) in the
HTTP/1.1 specification.

Dave Kristol
Received on Friday, 23 May 1997 14:23:19 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:43 EDT