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

Re: Allow is not in 13.5.2

From: Henrik Nordstrom <hno@squid-cache.org>
Date: Thu, 21 Dec 2006 02:24:29 +0100
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <1166664269.26316.130.camel@henriknordstrom.net>
ons 2006-12-20 klockan 16:55 -0800 skrev Travis Snoozy (Volt):

> The easy fix for now would be to just make a mention of allow in 13.5.2.

I would propose to also reduce the MUST NOT restriction in 14.7 down to
a SHOULD NOT which is more appropriate for this kind of restriction. Or
drop it entirely from there.

There is many scenarios where the proxy may actually know by
administrative policies outside the protocol that the user agent does
not have any other means of communication, so the assumption made in
14.7 is not necessarily true. MUST level requirements based on false
assumptions isn't that great.. Also, it does not make much sense to me
having this MUST requirement on non-transparent proxies.

So I propose the following


      A proxy MUST NOT modify the Allow header field even if it does not

changed to

      A proxy SHOULD NOT modify the Allow header field even if it does not

plus the already proposed 


"Allow" added to the first list of unmodifiable headers "A transparent
proxy MUST NOT modify"..

If 14.7 is kept as a MUST requirement then the directive needs to be
added in a new MUST section in 13.5.2 stricter than any of the existing


Received on Thursday, 21 December 2006 01:24:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 September 2019 17:47:10 UTC