- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 21 Jul 2008 18:59:35 +0200
- To: Ian Hickson <ian@hixie.ch>
- 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>
Ian Hickson wrote: >> Non-ASCII characters in header values are by definition ISO-8859-1. > > Well then the answer to your question is that you use ISO-8859-1 or > %-escaping. (And for legacy reasons, only %-escaping in the query part.) Not sure what these legacy reasons have to do with AC. Also, why you would ever want to use non-ASCII characters in an HTTP header when you need to percent-escape "most" code points anyway. >> It's not sufficient to encode all IRIs, thus you need to map >> IRIs to something you can use. > > ASCII is sufficient to encode all IRIs. Well, than the proposal should just state that people need to use RFC 3986 URIs, not the stuff HTML5 calls "URL". BR, Julian
Received on Monday, 21 July 2008 17:00:23 UTC