#24496: Check CSRF Referer against CSRF_TRUSTED_ORIGINS
------------------------------+------------------------------------
Reporter: mattrobenolt | Owner: joshkehn
Type: New feature | Status: assigned
Component: CSRF | Version: master
Severity: Normal | Resolution:
Keywords: csrf | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by joshkehn):
Updated PR based on comments, I'll update the attached patch as well after
this comment.
Regarding including the `CSRF_COOKIE_DOMAIN`, wouldn't that be required
anyways for the request to pass `ALLOWED_HOSTS`? I'm thinking that should
be checked after the `CSRF_TRUSTED_ORIGINS` check fails, correct? I'm
attaching two flows.
--
Ticket URL: <https://code.djangoproject.com/ticket/24496#comment:16>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.5d5a9ddee1b72ea042e5a0625ed0a542%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
