Re: parsing URI (references) according to RFC 3986

On 6/23/11 2:27 PM, Julian Reschke wrote:
> Using Firefox 5; looking at the "Net" tab under "Options" -> "Web
> Developer" -> "Web Console"; I just checked my server log and it does
> seem to be a bug in the tool.

Yeah, the Web Console doesn't know what actually went on the wire; it 
just synthesizes its information from some metadata about the network 
request... ;)

>> What needs testing is a document at
>> <http://greenbytes.de/tech/tc/uris/imgsame.html> with a <base
>> href="http://greenbytes.de/tech/tc/uris/imgother.html"> and an <img
>> src="#foo">.
>>
>> Per section 4.4 as I read it, and per your comments just now, that
>> should load http://greenbytes.de/tech/tc/uris/imgsame.html as an image.
>> Does anyone do that?
>
> ?
>
> 4.4 defers to section 5.1 for the definition of the base URI, and makes
> it media type dependent how to find it. So the HTML spec needs to answer
> that question (also, related questions with respect to changing the base
> URI after the document was loaded)-

There is no question about those aspects of this.  The base URI for the 
image source in this case is 
"http://greenbytes.de/tech/tc/uris/imgother.html".

> It doesn't. HTML needs to define it.

How can HTML define it without contradicting 4.4?  What's 4.4 even 
supposed to mean?

If it's not supposed to mean anything and specs that use URIs are just 
supposed to define what happens (a stance I agree with), then why is 4.4 
even there?

-Boris

Received on Thursday, 23 June 2011 18:32:19 UTC