#29858: Clarify docs regarding CSRF token header name
--------------------------------------+------------------------------------
Reporter: Stewart Polley | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* status: closed => new
* resolution: invalid =>
* has_patch: 0 => 1
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I see your point. The note was moved lower in
ddf169cdaca91e92dd5bfe6796bb6f38369ecb68 which didn't help. Could you
review my [https://github.com/django/django/pull/10529 PR]?
--
Ticket URL: <https://code.djangoproject.com/ticket/29858#comment:6>
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.a0d76e849b848cb7b74345c25a98a74a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
