#16870: CSRF too strict when no referer is present
------------------------+--------------------------------------
Reporter: rtux | Owner: nobody
Type: Bug | Status: new
Component: CSRF | Version: master
Severity: Normal | Resolution:
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 raulcd):
* status: closed => new
* resolution: wontfix =>
Comment:
Reopen bug so we take a look. I also think that things have changed since
the bug was open and due to new implementation of browsers the % of users
that may want to not send their HTTP_REFERER header may increase.
--
Ticket URL: <https://code.djangoproject.com/ticket/16870#comment:7>
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.1ae7f767578e1120bfcacb70d498a078%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
