Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reflect that GET, HEAD, and POST are always allowed methods #37266

Merged
merged 2 commits into from
Dec 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Access-Control-Allow-Methods: *
## Directives

- `<method>`
- : A comma-separated list of the allowed request methods.
- : A comma-separated list of the allowed request methods. `GET`, `HEAD`, and `POST` are always allowed, regardless of whether they are specified in this header, as they are defined as [CORS-safelisted method](https://fetch.spec.whatwg.org/#cors-safelisted-method)s.
bsmth marked this conversation as resolved.
Show resolved Hide resolved
- `*` (wildcard)
- : All HTTP methods.
It has this meaning only for requests without credentials (requests without [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) or HTTP authentication information). In requests with credentials, it is
Expand All @@ -41,7 +41,7 @@ Access-Control-Allow-Methods: *
## Examples

```http
Access-Control-Allow-Methods: GET, POST
Access-Control-Allow-Methods: PUT, DELETE
Access-Control-Allow-Methods: *
```

Expand Down
Loading