#25334: Check CSRF Referer against CSRF_TRUSTED_ORIGINS
-----------------------------+---------------------------------------------
Reporter: joshkehn | Owner: joshkehn
Type: New feature | Status: closed
Component: CSRF | Version: master
Severity: Normal | Resolution: fixed
Keywords: csrf | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+---------------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ab26b65b2f178597be845e203eb698e193e3502e" ab26b65b]:
{{{
#!CommitTicketReference repository=""
revision="ab26b65b2f178597be845e203eb698e193e3502e"
Fixed #25334 -- Provided a way to allow cross-origin unsafe requests over
HTTPS.
Added the CSRF_TRUSTED_ORIGINS setting which contains a list of other
domains that are included during the CSRF Referer header verification
for secure (HTTPS) requests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25334#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.79e3d51989a3b8b32b6c4a366519a4b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
