Skip to content

Commit d41ff4c

Browse files
authored
Suggest django-cors-middleware
Since `django-cors-headers` has been inactive since May 2015, the documentation should suggest using `django-cors-middleware`. This is a fork of `django-cors-headers` that has been kept up to date, so it supports django 1.10.
1 parent 46d136f commit d41ff4c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/tutorial/tutorial_01.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,14 @@ Start Your App
99
--------------
1010
During this tutorial you will make an XHR POST from a Heroku deployed app to your localhost instance.
1111
Since the domain that will originate the request (the app on Heroku) is different from the destination domain (your local instance),
12-
you will need to install the `django-cors-headers <https://github.com/ottoyiu/django-cors-headers>`_ app.
12+
you will need to install the `django-cors-middleware <https://github.com/zestedesavoir/django-cors-middleware>`_ app.
1313
These "cross-domain" requests are by default forbidden by web browsers unless you use `CORS <http://en.wikipedia.org/wiki/Cross-origin_resource_sharing>`_.
1414

15-
Create a virtualenv and install `django-oauth-toolkit` and `django-cors-headers`:
15+
Create a virtualenv and install `django-oauth-toolkit` and `django-cors-middleware`:
1616

1717
::
1818

19-
pip install django-oauth-toolkit django-cors-headers
19+
pip install django-oauth-toolkit django-cors-middleware
2020

2121
Start a Django project, add `oauth2_provider` and `corsheaders` to the installed apps, and enable admin:
2222

0 commit comments

Comments
 (0)