- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 21 Jul 2008 07:15:37 +0000 (UTC)
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Jonas Sicking <jonas@sicking.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 Mon, 21 Jul 2008, Julian Reschke wrote: > > Ian Hickson wrote: > > ... > > ...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. > > ... > > Correct. But it does allow non-ASCII characters. How do you put them > into an HTTP header value? Presumably HTTP defines how to handle non-ASCII characters in HTTP as part of its error handling rules, no? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 21 July 2008 07:16:21 UTC