- From: Ian Hickson <ian@hixie.ch>
- Date: Sun, 20 Jul 2008 23:19:38 +0000 (UTC)
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: Maciej Stachowiak <mjs@apple.com>, Sunava Dutta <sunavad@windows.microsoft.com>, "annevk@opera.com" <annevk@opera.com>, Sharath Udupa <Sharath.Udupa@microsoft.com>, Zhenbin Xu <Zhenbin.Xu@microsoft.com>, Gideon Cohn <gidco@windows.microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>, IE8 Core AJAX SWAT Team <ieajax@microsoft.com>
On Sun, 20 Jul 2008, Jonas Sicking wrote: > Ian Hickson wrote: > > On Sat, 19 Jul 2008, Jonas Sicking wrote: > > > According to the HTML5 spec space is a valid characted inside URLs. > > > > That wasn't intentional -- can you point to where it says that? The HTML5 > > spec relies on spaces not being allowed in URLs in various places. > > In section 2.3.2 (Parsing URLs): > > # Add all characters with codepoints less than or equal to U+0020 or > # greater than or equal to U+007F to the <unreserved> production. This is in the context of: # 2. Parse url in the manner defined by RFC 3986, with the following # exceptions: It isn't defining what's allowed. What's allowed is defined in the earlier section: # A URL is a valid URL if at least one of the following conditions holds: # ... ...which basically just says it's a valid URL if it's a valid URI or IRI (with some caveats in the case of IRIs to prevent legacy encoding behaviour from handling valid URLs in a way that contradicts the IRI spec). This doesn't allow spaces. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Sunday, 20 July 2008 23:20:15 UTC