Re: [whatwg] Resolving a URL

[Boris Zbarsky]

Ian Hickson wrote:

On Sun, 28 Dec 2008, Geoffrey Sneddon wrote:

Step 12 replaces \ with /. IIRC WebKit does this for all URLs, not just 
those with a "server-based naming authority" (what's that anyway?).


RFC 2396 section 3.2 (Authority Component) says:

  Many URI schemes include a top hierarchical element for a naming
  authority, such that the namespace defined by the remainder of the
  URI is governed by that authority. This authority component is
  typically defined by an Internet-based server or a scheme-specific
  registry of naming authorities.

So this is talking about URLs whose authority component is defined by an 
internet server (host + port, in practice).


-Boris

Re: [whatwg] Resolving a URL

[Ian Hickson]

On Sun, 28 Dec 2008, Geoffrey Sneddon wrote:
> 
> Step 3 is (currently) "If encoding is UTF-16, then change it to UTF-8.". 
> Does this mean we literally change just "encoding" to UTF-16, and leave 
> "url" verbatim, or are we meant to change "url" to UTF-8 too? This is 
> currently ambiguous. Not changing "url" will cause issues later in a 
> UTF-16 document.

I don't understand what it would mean for "url" to change to UTF-16. "url" 
is a sequence of characters at this point, it has no encoding.


> Step 12 replaces \ with /. IIRC WebKit does this for all URLs, not just 
> those with a "server-based naming authority" (what's that anyway?).

My testing suggests it doesn't:

   data:,/

See the URI specs for details.


> Also, earlier in the "Resolving URLs" section, there should probably be 
> a ref. to XMLBASE.

Ok.

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

[whatwg] Resolving a URL

[Geoffrey Sneddon]

Hey,

Time to send some feedback on the "resolve a URL" dfn.

Step 3 is (currently) "If encoding is UTF-16, then change it to  
UTF-8.". Does this mean we literally change just "encoding" to UTF-16,  
and leave "url" verbatim, or are we meant to change "url" to UTF-8  
too? This is currently ambiguous. Not changing "url" will cause issues  
later in a UTF-16 document.


Step 12 replaces \ with /. IIRC WebKit does this for all URLs, not  
just those with a "server-based naming authority" (what's that anyway?).


Also, earlier in the "Resolving URLs" section, there should probably  
be a ref. to XMLBASE.



--
Geoffrey Sneddon