#21495: Add a setting for CSRF Header name
-------------------------------------+-------------------------------------
Reporter: hello@… | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: 1.6
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
csrf,header,angularjs | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 0
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by timo):
As I noted on the [https://groups.google.com/d/topic/django-
developers/8bqbJ_6YArc/discussion mailing list thread]: "The main problem
I see with this approach is that it would no longer be straightforward for
3rd party code to access these settings. You'd need something akin to
get_user_model() to retrieve the currently installed CSRF middleware so
you could access its settings."
--
Ticket URL: <https://code.djangoproject.com/ticket/21495#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/077.188a883ab5e05eaf4845ea7d57c20399%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
