W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1997

Re: 305 Use proxy

From: Foteos Macrides <MACRIDES@sci.wfbr.edu>
Date: Mon, 24 Mar 1997 11:36:56 -0500 (EST)
To: kweide@tezcat.com
Cc: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2848
Klaus Weide <kweide@tezcat.com> wrote:
>On Sun, 23 Mar 1997, Roy T. Fielding wrote:
>> In message <199703202122.NAA03558@step.mcom.com>, Ari Luotonen writes:
>> >
>> >If 305 is allowed by origin servers, intermediate HTTP/1.1 proxies
>> >that do not understand 305's hop-by-hope requirement will let it
>> >through (I assume at this point it may be too late to impose the
>> >hop-by-hop requirement for 305, and expect it to be respected by all
>> >implementations).  If a client gets a 305 sent by an evil origin
>> >server through a proxy, it will override the client's proxy settings,
>> >because the client thinks the proxy redirected it to another proxy.
>> I don't know of any clients that have implemented 305.
>> Is it already in the Navigator (or other browser)?
>Lynx has implemented 305 for a while.  It only accepts it from an origin
>server (i.e. if not already using a proxy) and on a request-by-request
>basis (like 302; no "proxy settings" are overridden except for the
>current request).

	Note that this is another "better safe than sorry" initial
implementation in Lynx, reflecting concerns like those expressed
by Ari, but going beyond what was actually in the spec at the time
of the implementation.


 Foteos Macrides            Worcester Foundation for Biomedical Research
 MACRIDES@SCI.WFBR.EDU         222 Maple Avenue, Shrewsbury, MA 01545
Received on Monday, 24 March 1997 08:39:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:01 UTC