#26596: Document {{ csrf_input }} in Jinja2 templates
-------------------------------+-------------------------------------
Reporter: aaugustin | Owner: betojulio
Type: Bug | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+-------------------------------------
Comment (by aaugustin):
I believe this information would be more discoverable in the CSRF
reference documentation, either in the "How to use it" section or in a new
section.
We should talk about:
- the API offered by built-in template backends
- requirements for third-party backends, as described in PEP 182
(basically they have to provide a solution, but that solution isn't
specified)
This will likely require tweaking the content a bit to clarify that the
main examples are specific to Django templates.
--
Ticket URL: <https://code.djangoproject.com/ticket/26596#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 [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/067.6baa9c6468246715cea3244e46b5fb7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
