Re: Is this use of BASE kosher?

Peter K. Sheerin (
Wed, 2 Aug 95 17:04:33 EDT

> > But my question is a little more specific. Should #fragments be counted
> > as part of the URL for the specific purpose of determining whether they
> > always refer to the current document, or are appended to whatever the
> > value of the BASE URL is?
> The only thing that makes sense to me is that HREF="#fragment"
> references should refer to the current document, even though any other
> references HREF="../c#fragment" are relative to the base.

That's the only way it makes sense to me, but I don't see that spelled
out in the spec, and even RFC 1808 appears to conflict itself. It says
that fragment identifiers are not part of the URL, but then includes an
example in section 5.1 where a stand-along fragment identifier is merged
with the BASE URL (although it's not clear if this is the current
document's default URL or the BASE URL present in the header -- it
shouldn't matter, except that we are indeed talking about treating
stand-alone fragment identifiers differently from partial (relative) URLs).

Since the two biggest browsers handle this situation differently right
now, I submit that we should produce language defining a sensible
behaviour, since there seems to be no common behaviour to document. But
does this wait for 3.0, or could it go into 2.1, or am I missing wording
somewhere in this morass of RFCs, and SGML and HTML specs that defines
behaviour here?