- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 05 Sep 2008 10:13:12 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: Jonas Sicking <jonas@sicking.cc>, Sunava Dutta <sunavad@windows.microsoft.com>, Maciej Stachowiak <mjs@apple.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>
Anne van Kesteren wrote: > ... > Using the latter is non-conforming for Origin and also non-conforming > for Access-Control-Allow-Origin, which per its current definition either > mathces Origin literally or is a wildcard. So currently RFC 2047 > extensions are simply not supported (and not needeD) by the > specification. Given that interoperability on encoded-word is very poor > I suggest we keep it that way. > ... By all means, please do so. Maybe add a warning that RFC 2047 encoding is *not* allowed? BR, Julian
Received on Friday, 5 September 2008 08:14:05 UTC