- From: Vladimir Dzhuvinov <vladimir@dzhuvinov.com>
- Date: Fri, 24 Sep 2010 17:02:18 +0300
- Cc: public-webapps@w3.org
>> The CORS draft on the other hand requires case-sensitive matching of >> origins: >> >> http://www.w3.org/TR/access-control/#resource-requests > > It requires case-sensitive matching of the serialization of origins. They > are never parsed into origins to begin with. Does this mean that the value of the origin header should be treated as an arbitrary string? Because if I don't parse the origin value I have no mean of knowing that it actually represents a valid origin. Vladimir -- Vladimir Dzhuvinov :: software.dzhuvinov.com
Received on Friday, 24 September 2010 14:09:05 UTC