#34888: CSRF verification failed in django 4 when nginx serves the webserver
-------------------------------------+-------------------------------------
Reporter: Muhammad Fazel | Owner: nobody
Samarghandi |
Type: Bug | Status: closed
Component: CSRF | Version: 4.2
Severity: Normal | Resolution: needsinfo
Keywords: csrf | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
You've not explained why Django is at fault. Perhaps
[https://docs.djangoproject.com/en/dev/releases/4.0/#csrf-trusted-origins-
changes the CSRF_TRUSTED_ORIGINS changes] in Django 4.0 are relevant. See
TicketClosingReasons/UseSupportChannels if you need help debugging your
issue, and reopen if you can explain why Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/34888#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018afbd482d1-04dcc174-917f-4784-bb2f-d78cbabb2c16-000000%40eu-central-1.amazonses.com.
