Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Delivered-To: mailing list new-httpd@apache.org
Received: (qmail 36316 invoked from network); 21 Feb 2000 23:20:28 -0000
Received: from gremlin.ics.uci.edu (mmdf@128.195.1.70)
  by locus.apache.org with SMTP; 21 Feb 2000 23:20:28 -0000
Received: from kiwi.ics.uci.edu  ( fielding@kiwi.ics.uci.edu [128.195.21.109]
 )
          by gremlin-relay.ics.uci.edu id aa13342 for <new-httpd@apache.org>;
          21 Feb 2000 15:20 PST
To: new-httpd@apache.org
Subject: Re: [Patch] Content-Location headers stripped by reverse proxy 
In-reply-to: Your message of "Mon, 21 Feb 2000 22:06:54 GMT."
             <38B1B6FE.69BB965A@algroup.co.uk>
Date: Mon, 21 Feb 2000 15:20:26 -0800
From: "Roy T. Fielding" <fielding@kiwi.ICS.UCI.EDU>
Message-ID: <200002211520.aa13342@gremlin-relay.ics.uci.edu>

>I think if you want any chance of this kind of thing being accepted
>you're going to have to make a general purpose "strip these headers when
>proxying" thing. I certainly can't see us always stripping
>Content-Location simply because some phone companies can't implement
>their browsers correctly.

The browser is correct.  The problem is that our hack gateway
("reverse proxy") is not correctly translating the response.
Translating the content-location field would be better, but stripping
it is acceptable.

....Roy