W3C home > Mailing lists > Public > www-talk@w3.org > September to October 2000

re: Connection: close (was: Re: Msg header)

From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Date: Sat, 02 Sep 2000 13:00:53 +0100
Message-Id: <s9b0fc00.030@tapsellferrier.co.uk>
To: fish@infidels.org, www-talk@w3.org
>>> "Fish" <fish@infidels.org> 02-Sep-00 5:08:32 AM >>
>I respectfully disagree.
>While RFC 2616 doesn't mention specifically how to 
>handle such a situation, it does mention that the order 
>of individual field values for a given header *is* significant.
>Thus I would think that common sense would prevail in 
>such a situation and the each subsequent new occurrence 
>of given field value would override any previous value so in 
>the example Jim provided, "keepalive" would override
> (i.e. replace) the previously supplied "close" value.

Where are you getting that from. I can only see this in RFC2616
section 4.2:

"Multiple message-header fields with the same field-name MAY be
present in a message if and only if the entire field-value for that
header field is defined as a comma-separated list [i.e., #(values)].
It MUST be possible to combine the multiple header fields into one
"field-name: field-value" pair, without changing the semantics of
the
message, by appending each subsequent field-value to the first, each
separated by a comma. The order in which header fields with the same
field-name are received is therefore significant to the
interpretation of the combined field value, and thus a proxy MUST
NOT
change the order of these field values when a message is forwarded."

The important bit here is the "it MUST be possible to combine the
multiple header fields" which is contravened by sending two opposing
header fields.

Anyway, my reading of RFC2616 section 8.1.2 and 8.1.2.1 is that if
the "close" token is present for the "Connection" header then the
connection MUSR be closed. 

In the example given the "close" token is present, so the
"Connection" *must* be closed.


Nic
Received on Saturday, 2 September 2000 08:03:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT