Re: HTTP 1.1 Issue: When To Close Connections

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Yaron Goland: "RE: PEP Integration in RTSP"
• Previous message: Yaron Goland: "RE: PEP Integration in RTSP"
• Maybe in reply to: John C. Mallery: "HTTP 1.1 Issue: When To Close Connections"
• Next in thread: Larry Masinter: "Re: HTTP 1.1 Issue: When To Close Connections"

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

• Next message: Yaron Goland: "RE: PEP Integration in RTSP"
• Previous message: Yaron Goland: "RE: PEP Integration in RTSP"
• Maybe in reply to: John C. Mallery: "HTTP 1.1 Issue: When To Close Connections"
• Next in thread: Larry Masinter: "Re: HTTP 1.1 Issue: When To Close Connections"