#16870: CSRF too strict when no referer is present
------------------------+--------------------------------------
Reporter: rtux | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------+--------------------------------------
Changes (by jdufresne):
* cc: jon.dufresne@… (added)
* version: 1.5 => master
Comment:
This issue came up recently on django-developers:
https://groups.google.com/forum/#!msg/django-
developers/4ZDBMulE-W0/_iKRIGctxccJ
One recent development that makes this more of a concern than in the past
is the new HTML referrer tag:
https://blog.mozilla.org/security/2015/01/21/meta-referrer/
--
Ticket URL: <https://code.djangoproject.com/ticket/16870#comment:6>
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/062.1e7867174db43285e73346af2ce41e3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
