#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 betojulio):

 >{% csrf_token %} in Django templates translates to {{ csrf_input }} in
 Jinja2 templates

 This is already specified in
 https://docs.djangoproject.com/en/dev/ref/csrf/#other-template-engines

 >{{ csrf_token }} works identically in Django templates and in Jinja2
 templates
 Should I put another example in step # 2 in
 https://docs.djangoproject.com/en/dev/ref/csrf/#how-to-use-it ?, something
 like


 {{{
 <div style="display:none">
     <input type="hidden" name="csrfmiddlewaretoken" value="{{ csrf_token
 }}">
 </div>
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26596#comment:8>
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/067.4650c9115d7402a94a4b4a57c054b9ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to