#12738: CSRF token name should be a configurable setting
-------------------------------------+-------------------------------------
Reporter: German M. Bravo | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: CSRF | Version:
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 Tim Graham):
* type: Uncategorized => Cleanup/optimization
* component: Uncategorized => CSRF
Comment:
A [https://github.com/django/django/pull/10305 PR] implemented this with
rationale
"[https://github.com/AliasIO/Wappalyzer/blob/f5a77f3453c796c66f3e597fb30edbc3e2a285c8/src/apps.json#L2471
Wappalyzer] identifies Django application with "csrfmiddlewaretoken" input
name."
I wrote to [https://groups.google.com/d/topic/django-
developers/V8-ifC7i_nU/discussion django-developers] to see if there's
consensus to reopen this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/12738#comment:5>
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/064.bf888cd6b8691a84aa6251545e555931%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
