kennethreitz/responder
1
0
Fork 0
mirror of https://github.com/kennethreitz/responder.git synced 2026-06-05 23:00:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #156 from taoufik07/patch-11

Browse Source 
Fix link formatting
This commit is contained in:
Kenneth Reitz
2018-10-25 18:12:36 -04:00
committed by GitHub
parent f9d55fc425 1e6c9d935a
commit 090a3a571b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/source/tour.rst
+2 -2
View File
@@ -208,7 +208,7 @@ Boom.
CORS
----
Want [CORS headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) ?
Want `CORS <https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/>`_ ?
::
@@ -217,7 +217,7 @@ Want [CORS headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) ?
The default parameters used by **Responder** are restrictive by default, so you'll need to explicitly enable particular origins, methods, or headers, in order for browsers to be permitted to use them in a Cross-Domain context.
In order to set your custom parameters, you need to pass the ``cors_params`` argument, a dictionnary containing the following entries :
In order to set custom parameters, you need to pass the ``cors_params`` argument, a dictionnary containing the following entries :
* ``allow_origins`` - A list of origins that should be permitted to make cross-origin requests. eg. ``['https://example.org', 'https://www.example.org']``. You can use ``['*']`` to allow any origin.
* ``allow_origin_regex`` - A regex string to match against origins that should be permitted to make cross-origin requests. eg. ``'https://.*\.example\.org'``.