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

Re: NEW ISSUE: Drop Content-Location

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 29 Nov 2006 22:44:29 +0100
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
Message-ID: <op.tjsr0f2n64w2qv@id-c0020.oslo.opera.com>

On Wed, 29 Nov 2006 22:40:25 +0100, Julian Reschke <julian.reschke@gmx.de>  
> From what I see the problem was that many deployed servers return a  
> Content-Location header containing a URI which in fact isn't accessible  
> from the outside. That's a server bug.

I'm sure you read https://bugzilla.mozilla.org/show_bug.cgi?id=109553#c37  
as well which suggests otherwise. Also, whether it's servers or clients  
that are broken doesn't really matter. The simple fact is that the header  
can't be supported.

> The header allows relative URIs, so it seems to me it would be safe for  
> user agents to support the header if - for instance - it's an absolute  
> path. That should still cover the majority of the use cases...

 From my recollection we can't really implement it in any way.

Anne van Kesteren
Received on Wednesday, 29 November 2006 21:44:40 UTC

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