Generify how OPTIONS and CORS are handled
This commit is contained in:
parent
dd9414472b
commit
423d5593f5
1 changed files with 2 additions and 4 deletions
|
@ -173,10 +173,8 @@ to pre-flight requests and supply Cross-Origin Resource Sharing (CORS) headers o
|
||||||
all requests.
|
all requests.
|
||||||
|
|
||||||
When a client approaches the server with a pre-flight (``OPTIONS``) request, the
|
When a client approaches the server with a pre-flight (``OPTIONS``) request, the
|
||||||
server should respond with the CORS headers for that route. If the route does not
|
server should respond with the CORS headers for that route. The recommended CORS
|
||||||
exist, the server should return an ``M_NOT_FOUND`` error with a 404 status code.
|
headers to be returned by servers on all requests are:
|
||||||
|
|
||||||
The standard CORS headers to be returned by servers on all requests are:
|
|
||||||
|
|
||||||
.. code::
|
.. code::
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue