#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
------------------------+--------------------------------------
Comment (by aaugustin):
Perhaps we should document that Django's CSRF protection is incompatible
with `<meta name="referrer" content="none">` and requires at least the
origin for same-site requests (in which case there are no privacy
concerns).
--
Ticket URL: <https://code.djangoproject.com/ticket/16870#comment:10>
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.21fc41ba7925730e6050c859bb2d1a34%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
