Skip to content

Commit

Permalink
Clarify allowed HTTP methods in CORS responses (take 2)
Browse files Browse the repository at this point in the history
Signed-off-by: Kévin Commaille <[email protected]>
  • Loading branch information
zecakeh committed Nov 21, 2024
1 parent d67dd88 commit 10f4461
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions content/client-server-api/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -314,11 +314,17 @@ respond with the CORS headers for that route. The recommended CORS
headers to be returned by servers on all requests are:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, PATCH, HEAD
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Headers: X-Requested-With, Content-Type, Authorization

{{% changed-in v="1.13" %}} `PATCH` and `HEAD` were added to the list for the
`Access-Control-Allow-Methods` header.
{{% boxes/note %}}
{{% added-in v="1.13" %}} The recommended value of the `Access-Control-Allow-Methods`
header only covers the existing endpoints in the specification. Servers which
support additional endpoints or methods should add those methods as well.

This section will be updated whenever a new method is supported by an endpoint.
Examples of possible future-use methods include `PATCH` and `HEAD`.
{{% /boxes/note %}}

## Server Discovery

Expand Down

0 comments on commit 10f4461

Please sign in to comment.