- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 15 Sep 2015 22:44:01 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
Received on Wednesday, 16 September 2015 05:44:31 UTC
How is this different from content negotiation, where you need to know what headers to supply to get a particular representation? And failing to supply headers might result in an error? In any event, "follow your nose" hasn't really come up as a problem with CORS thus far. And redesigning CORS at this point does not seem feasible. We could do something additive, but that doesn't really solve the problem for the existing content, so it's unclear to me what can be done here, realistically. --- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/76#issuecomment-140633701
Received on Wednesday, 16 September 2015 05:44:31 UTC