#25368: Rename X_CSRFTOKEN to X-CSRFTOKEN
-------------------------------------+-------------------------------------
Reporter: belegnar | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: CSRF | Version: 1.8
Severity: Normal | Resolution: invalid
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 timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi, I think you've [https://docs.djangoproject.com/en/1.8/ref/request-
response/#django.http.HttpRequest.META missed the documentation] on how
Django treats HTTP headers:
any HTTP headers in the request are converted to `META` keys by
converting all characters to uppercase, replacing any hyphens with
underscores and adding an `HTTP_` prefix to the name. So, for example, a
header called `X-Bender` would be mapped to the META key `HTTP_X_BENDER`.
--
Ticket URL: <https://code.djangoproject.com/ticket/25368#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.b068756c4eb64ff9c8a3caed83d5983c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
