p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed some typos 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11668 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2009-10-27 13:13:40 +00:00
parent f00ad4168e
commit b32a187296
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ref/contrib/csrf.txt
View File

@ -89,7 +89,7 @@ Legacy method
------------- -------------
In Django 1.1, the template tag did not exist. Instead, a post-processing In Django 1.1, the template tag did not exist. Instead, a post-processing
middleware that re-wrote POST forms to include the CRSF token was used. If you middleware that re-wrote POST forms to include the CSRF token was used. If you
are upgrading a site from version 1.1 or earlier, please read this section and are upgrading a site from version 1.1 or earlier, please read this section and
the `Upgrading notes`_ below. The post-processing middleware is still available the `Upgrading notes`_ below. The post-processing middleware is still available
as ``CsrfResponseMiddleware``, and it can be used by following these steps: as ``CsrfResponseMiddleware``, and it can be used by following these steps:
@ -108,7 +108,7 @@ as ``CsrfResponseMiddleware``, and it can be used by following these steps:
Use of the ``CsrfResponseMiddleware`` is not recommended because of the Use of the ``CsrfResponseMiddleware`` is not recommended because of the
performance hit it imposes, and because of a potential security problem (see performance hit it imposes, and because of a potential security problem (see
below). It can be used as an interim measure until applications have been below). It can be used as an interim measure until applications have been
updated to use the ``{% crsf_token %}`` tag. It is deprecated and will be updated to use the ``{% csrf_token %}`` tag. It is deprecated and will be
removed in Django 1.4. removed in Django 1.4.
Django 1.1 and earlier provided a single ``CsrfMiddleware`` class. This is also Django 1.1 and earlier provided a single ``CsrfMiddleware`` class. This is also