#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: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: 0 => 1
Comment:
The idea of moving settings into middleware has been thoroughly rejected
on [https://groups.google.com/d/topic/django-
developers/t8ybImtdnpM/discussion a django-developers thread] discussing
integrating django-secure's middleware. If it can be done in a backwards
compatible way, maybe it would make sense to group the CSRF settings into
a dictionary as suggested in the thread. See #22734 which discusses doing
this for the SMTP & email settings and also has a patch with proof of
concept code.
--
Ticket URL: <https://code.djangoproject.com/ticket/21495#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/077.8d4f6135447ba2e687f40d0f7f3d968a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
