#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 ubernostrum):
* status: new => closed
* resolution: => wontfix
Comment:
Per the ticket/triaging documentation, do not re-open a ticket which has
been closed "wontfix" by a member of the Django core team:
https://docs.djangoproject.com/en/1.7/internals/contributing/triaging-
tickets/#closing-tickets
--
Ticket URL: <https://code.djangoproject.com/ticket/16870#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 [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.6d2a16c548d0b8509669c4e48ce9ac43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
