179
Check if you are using Django 4.0. I was using 3.2 and had this break for the upgrade to 4.0.
If you are on 4.0, this was my fix. Add this line to your settings.py
. This was not required when I was using 3.2 and now I can’t POST a form containing a CSRF without it.
CSRF_TRUSTED_ORIGINS = ['https://*.mydomain.com','https://*.127.0.0.1']
Review this line for any changes needed, for example if you need to swap out https
for http
.
Root cause is the addition of origin header checking in 4.0.
https://docs.djangoproject.com/en/4.0/ref/settings/#csrf-trusted-origins
Changed in Django 4.0:
Origin header checking isn’t performed in older versions.
50
Mar, 2022 Update:
If your django version is "4.x.x":
python -m django --version
// 4.x.x
Then, if the error is as shown below:
Origin checking failed – https://example.com does not
match any trusted origins.
Add this code to "settings.py":
CSRF_TRUSTED_ORIGINS = ['https://example.com']
In your case, you got this error:
Origin checking failed – https://praktikum6.jhoncena.repl.co does not
match any trusted origins.
So, you need to add this code to your "settings.py":
CSRF_TRUSTED_ORIGINS = ['https://praktikum6.jhoncena.repl.co']
- [Django]-How to get the label of a choice in a Django forms ChoiceField?
- [Django]-How to stop gunicorn properly
- [Django]-Get list item dynamically in django templates
50
Origin and host are the same domain
If, like me, you are getting this error when the origin and the host are the same domain.
It could be because:
- You are serving your django app over HTTPS,
- Your django app is behind a proxy e.g. Nginx,
- You have forgotten to set SECURE_PROXY_SSL_HEADER in your
settings.py
e.g.SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
and/or - You have forgotten to set the header in your server configuration e.g.
proxy_set_header X-Forwarded-Proto https;
for Nginx.
In this case:
- The origin header from the client’s browser will be
https://www.example.com
due to 1. request.is_secure()
is returningFalse
due to 2, 3 and 4.- Meaning
_origin_verified()
returnsFalse
because of line 285 of django.middleware.csrf (comparison ofhttps://www.example.com
tohttp://www.example.com
):
def _origin_verified(self, request):
request_origin = request.META["HTTP_ORIGIN"]
try:
good_host = request.get_host()
except DisallowedHost:
pass
else:
good_origin = "%s://%s" % (
"https" if request.is_secure() else "http",
good_host,
)
if request_origin == good_origin:
return True
Make sure you read the warning in https://docs.djangoproject.com/en/4.0/ref/settings/#secure-proxy-ssl-header before changing this setting though!
- [Django]-How do I convert datetime.timedelta to minutes, hours in Python?
- [Django]-Missing Table When Running Django Unittest with Sqlite3
- [Django]-Django: Catching Integrity Error and showing a customized message using template
0
You can also have this error because you are using a container on Proxmox.
If your https domain name is routed by Proxmox via an internal http connection you will have this error.
DOMAIN NAME (https) => Proxmox => (http) => Container with Django : CSRF ERROR
I had this error, and change the routing via Proxmox to my container via an https internal connection (I had to create and sign a certificate on my CT).
DOMAIN NAME (hhtps) => Proxmox => (https) => Container with Django
Since the CSRF error on Django disappeared.
- [Django]-Django Rest framework, how to include '__all__' fields and a related field in ModelSerializer ?
- [Django]-How to configure where to redirect after a log out in Django?
- [Django]-How does Django's nested Meta class work?