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
When running this behind a reverse proxy, e.g. when using the docker compose setup we need to set the CSRF_TRUSTED_ORIGINS setting since the connection between the nginx in the docker compose and the application is not encrypted.
This can probably be solved with a better configured proxy but we first need a setup so this can be more easily reproduced, etc. etc.
As an additional datapoint - I received this today after deploying on kubernetes with an istio service mesh / ingress-gateway providing my tls termination.
When running this behind a reverse proxy, e.g. when using the docker compose setup we need to set the CSRF_TRUSTED_ORIGINS setting since the connection between the nginx in the docker compose and the application is not encrypted.
This can probably be solved with a better configured proxy but we first need a setup so this can be more easily reproduced, etc. etc.
See #1203
https://stackoverflow.com/questions/70679571/how-do-i-set-a-wildcard-for-csrf-trusted-origins-in-django
https://docs.djangoproject.com/en/4.1/ref/settings/#secure-proxy-ssl-header
The text was updated successfully, but these errors were encountered: