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

Re: Content-Location as Base URI

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Mon, 10 Dec 2007 10:46:58 +0100
To: "L. David Baron" <dbaron@dbaron.org>
Cc: ietf-http-wg@w3.org
Message-Id: <1197280018.27305.6.camel@henriknordstrom.net>
On mån, 2007-12-10 at 00:41 -0800, L. David Baron wrote:
> On Monday 2007-12-10 06:34 +0100, Henrik Nordstrom wrote:
> > But browser vendors do not dare implementing it due to there being a
> > handful number of noticeably broken servers out there sending
> It's not just broken servers.  With the list of Mozilla's
> Content-Location bugs:
> https://bugzilla.mozilla.org/showdependencytree.cgi?id=238654&maxdepth=1&hide_resolved=0
> I found one bug that's not about a broken server:
> https://bugzilla.mozilla.org/show_bug.cgi?id=241981
> It's about Apache serving a content-negotiated document at a URL of
> the form http://example.com/doc .  For browsers supporting XHTML, it
> serves doc.xhtml; for other browsers, it serves an equivalent
> doc.html.  The document contains links to anchors within itself
> (e.g., <a href="#intro">Introduction</a>); links in the document are
> relative to Content-Location.  Thus, clicking one of those links
> takes the browser to http://example.com/doc.xhtml#intro, which is
> not a URL intended to be linked to or exchanged.

Which is a minor Mozilla implementation bug, as anchor links with an
empty relative reference is within the current document.
Content-Location, base href or any other means of specifying the
intended location of the current document should not change that.

rfc3986 setion 4.4.

Content-Location (and base href) does not change the location of the
object, only the Base-URI.


Received on Monday, 10 December 2007 09:47:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:44 UTC