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

RE: i15: How to tell if a client does not support persistent connections

From: Paul Leach <paulle@windows.microsoft.com>
Date: Fri, 14 Dec 2007 15:45:23 -0800
To: Henrik Nordstrom <henrik@henriknordstrom.net>, Lisa Dusseault <lisa@osafoundation.org>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <920B8B05FB49A04699188E04302FE87D4AF43C213F@NA-EXMSG-W602.wingroup.windeploy.ntdev.microsoft.com>

If adding this as a MUST can make existing compliant HTTP/1.1 clients non-compliant, then I think that it's outside what the WG charter allows (and logically would require a new minor version of HTTP, would it not?).

-----Original Message-----
From: ietf-http-wg-request@w3.org [mailto:ietf-http-wg-request@w3.org] On Behalf Of Henrik Nordstrom
Sent: Thursday, December 13, 2007 6:16 AM
To: Lisa Dusseault
Cc: HTTP Working Group

On ons, 2007-12-12 at 18:48 -0800, Lisa Dusseault wrote:
> Issue i15 is closed, and the resolution suggests new text, in part:
>       "An HTTP/1.1 client that does not support persistent connections MUST
> include the "close" connection option in every request message. "

>From what I understand it's a MUST to align the rules with server side.

But it's true that it doesn't need to be a MUST on the client side. A SHOULD is quite sufficient.

Received on Friday, 14 December 2007 23:45:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:44 UTC