wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify allowed HTTP methods in CORS responses (take 2) (#2011)

Browse source 
* Clarify allowed HTTP methods in CORS responses (take 2)

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>

* Update previous changelog an add duplicate changelog

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>

---------

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2024-12-11 18:21:49 +01:00 • committed by GitHub
parent 9198182f1a
commit 846cc49eb2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 11 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
content/client-server-api/_index.md
View file

@ -322,11 +322,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