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
In Django 4.0+, we now have to provide the scheme http:// or https:// with trusted origins as well. Read the following docs for more info. So to keep compatibility with Django 3.2 as we are currently on this version, we need to add a separate variable in YAML and add the condition to pick that variable once we reach Django 4.
In YAMLs
For example if currently CSRF_TRUSTED_ORIGINS looks like this
CSRF_TRUSTED_ORIGINS:
- .edx.org
Add a new variable CSRF_TRUSTED_ORIGINS_WITH_SCHEMES like this.
In Django 4.0+, we now have to provide the scheme
http://
orhttps://
with trusted origins as well. Read the following docs for more info. So to keep compatibility with Django 3.2 as we are currently on this version, we need to add a separate variable in YAML and add the condition to pick that variable once we reach Django 4.In YAMLs
For example if currently
CSRF_TRUSTED_ORIGINS
looks like thisAdd a new variable
CSRF_TRUSTED_ORIGINS_WITH_SCHEMES
like this.In IDA's settings file (mostly production.py)
We need to have conditional settings for Django 4.
Release notes: https://docs.djangoproject.com/en/4.2/releases/4.0/#csrf-trusted-origins-changes
Django 4.0 Docs: https://docs.djangoproject.com/en/4.0/ref/settings/#csrf-trusted-origins
Django 3.2 Docs: https://docs.djangoproject.com/en/3.2/ref/settings/#csrf-trusted-origins
IDAs
The text was updated successfully, but these errors were encountered: