Fixed #12350 -- Fixed typo in tutorial04. Thanks, mortense
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12173 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
1f400c6df0
commit
985dcdb4b2
|
@ -47,12 +47,12 @@ A quick rundown:
|
||||||
* ``forloop.counter`` indicates how many times the :ttag:`for` tag has gone
|
* ``forloop.counter`` indicates how many times the :ttag:`for` tag has gone
|
||||||
through its loop
|
through its loop
|
||||||
|
|
||||||
* Since we are creating a POST form (which can have the effect of modifying
|
* Since we're creating a POST form (which can have the effect of modifying
|
||||||
data), we unfortunately need to worry about Cross Site Request Forgeries.
|
data), we need to worry about Cross Site Request Forgeries.
|
||||||
Thankfully, you don't have to worry too hard, because Django comes with
|
Thankfully, you don't have to worry too hard, because Django comes with
|
||||||
very easy-to-use system for protecting against it. In short, all POST
|
a very easy-to-use system for protecting against it. In short, all POST
|
||||||
forms that are targetted at internal URLs need the ``{% csrf_token %}``
|
forms that are targeted at internal URLs should use the ``{% csrf_token %}``
|
||||||
template tag adding.
|
template tag.
|
||||||
|
|
||||||
The ``{% csrf_token %}`` tag requires information from the request object, which
|
The ``{% csrf_token %}`` tag requires information from the request object, which
|
||||||
is not normally accessible from within the template context. To fix this, a
|
is not normally accessible from within the template context. To fix this, a
|
||||||
|
|
Loading…
Reference in New Issue