- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 17 Feb 2015 20:24:18 +0100
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: WebAppSec WG <public-webappsec@w3.org>, WebApps WG <public-webapps@w3.org>, Monsur Hossain <monsur@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Dale Harvey <dale@arandomurl.com>
On Tue, Feb 17, 2015 at 8:18 PM, Bjoern Hoehrmann <derhoermi@gmx.net> 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. -- https://annevankesteren.nl/
Received on Tuesday, 17 February 2015 19:24:48 UTC