- 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>
On Wed, 29 Nov 2006 22:40:25 +0100, Julian Reschke <julian.reschke@gmx.de> wrote: > 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 <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Wednesday, 29 November 2006 21:44:40 UTC