>> 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
