ISSUE-14: Opting into methods/headers


Opting into methods/headers

HISTORICAL: CORS [this spec uses Bugzilla for Bug/Issue tracking]
Raised by:
Anne van Kesteren
Opened on:
[[ This issue was created on 2008-06-06 as Issue #27 in the Web Applications Formats (WAF) WG and is copied in totality to the Web Applications WG's Issues database:
<> ]]

The current Access Control model allows all methods to be used and all headers (apart from a blacklist and some headers require a preflight request in case of GET).

There is a proposal to only allow methods and headers the server has opted into:

[AC] Helping server admins not making mistakes

This would make the server more secure by default when opting into Access Control.

The drawback is again that it makes the model more complicated and more prone to bugs.
Related Actions Items:
No related actions
Related emails:
  1. [access-control] Proposal to Close Issue#14 - Opting into methods/headers (from on 2008-10-09)
  2. [access-control] Issue list (from on 2008-07-08)
  3. ISSUE-14 (opt-into-methods-headers): Opting into methods/headers [Access Control] (from on 2008-06-23)

Related notes:

Closed. See:

Arthur Barstow, 21 Oct 2008, 16:04:49

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 14.html,v 1.1 2016/01/25 10:26:15 carine Exp $