You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/installation.rst
+37Lines changed: 37 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,3 +110,40 @@ need to be updated. This can be achieved, for example, by installing or
110
110
updating the ``mailcap`` package on a Red Hat distribution, ``mime-support`` on
111
111
a Debian distribution, or by editing the keys under ``HKEY_CLASSES_ROOT`` in
112
112
the Windows registry.
113
+
114
+
Cross-Origin Request Blocked
115
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
116
+
117
+
The Debug Toolbar loads a `JavaScript module`_. Typical local development using
118
+
Django ``runserver`` is not impacted. However, if your application server and
119
+
static files server are at different origins, you may see `CORS errors`_ in
120
+
your browser's development console:
121
+
122
+
.. code-block:: text
123
+
124
+
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost/static/debug_toolbar/js/toolbar.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
125
+
126
+
Or
127
+
128
+
.. code-block:: text
129
+
130
+
Access to script at 'http://localhost/static/debug_toolbar/js/toolbar.js' from origin 'http://localhost:8000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
131
+
132
+
To resolve, configure your static files server to add the
133
+
`Access-Control-Allow-Origin header`_ with the origin of the application
134
+
server. For example, if your application server is at ``http://example.com``,
0 commit comments