#16704: Documentation on using csrf_token with non-Django template engine
----------------------------+-------------------------------
Reporter: vietjtnguyen@… | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Documentation
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 1
UI/UX: 0 |
----------------------------+-------------------------------
I've been teaching myself Django today by going through your tutorials.
The system is great! The tutorials are great as well. Thank you very much.
I'm a big fan of the Cheetah template engine so from the get-go I've been
trying to set up my Django to use Cheetah. One thing I noticed though is
the Django template engine has a special handler for the `{% csrf_token
%}` token. I had to delve into the handler for that token to figure out
what to do for Cheetah. I think it's worth adding to the documentation
that if they're using a non-Django template engine they should use the
following HTML code in lieu of the `{% csrf_token %}`:
{{{
<div style="display:none"><input type="hidden" name="csrfmiddlewaretoken"
value="$csrf_token"/></div>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16704>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
