W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: XDomainRequest Integration with AC

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 21 Jul 2008 09:24:13 +0200
Message-ID: <4884399D.4020909@gmx.de>
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:
> 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?

Non-ASCII characters in header values are by definition ISO-8859-1. Yes, 
that sucks. It's not sufficient to encode all IRIs, thus you need to map 
IRIs to something you can use.

And no, that has nothing to do with error handling.

BR, Julian
Received on Monday, 21 July 2008 07:24:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT