Re: CORS performance

+1 to Anne's suggestion. The current design is pretty terrible for API
performance. I think a request to / with OPTIONS or something, with a
response that requires some server side logic (like return the random
number UA just sent) is pretty darn secure.


On 17 February 2015 at 11:24, Anne van Kesteren <> wrote:
> On Tue, Feb 17, 2015 at 8:18 PM, Bjoern Hoehrmann <> wrote:
>> Individual resources should not be able to declare policy for the whole
>> server, ...
> With HSTS we gave up on that.
>> HTTP/1.1 rather has `OPTIONS *` for that, which would require a
>> new kind of "preflight" request. And if the whole server is fine with
>> cross-origin requests, I am not sure there is much of a point trying to
>> lock it down by restricting request headers or methods.
> Yeah, I wasn't sure whether those should all be listed. Maybe simply
> declaring you're fluent in CORS in a unique way is sufficient.
> --

Received on Tuesday, 17 February 2015 19:33:32 UTC