diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2008-12-03 00:44:12 +0000 |
|---|---|---|
| committer | Luke Plant <L.Plant.98@cantab.net> | 2008-12-03 00:44:12 +0000 |
| commit | 9ec9936413a906e71ce79d1ce7d26df865891a95 (patch) | |
| tree | b9daf6c4831510c15aaa8fee43734a814df34f22 | |
| parent | 9eedc7bd0b21c936a30f000ba876dbcf5c0bed50 (diff) | |
Updated csrf docs with 'versionadded' info
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9555 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/ref/contrib/csrf.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index feb91f65d8..f83fc6e438 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -32,6 +32,8 @@ list. Exceptions ---------- +.. versionadded:: 1.1 + To manually exclude a view function from being handled by the CsrfMiddleware, you can use the ``csrf_exempt`` decorator (found in the ``django.contrib.csrf.middleware`` module). @@ -82,6 +84,10 @@ classes: ``CsrfResponseMiddleware`` and ``CsrfViewMiddleware`` respectively. This allows the individual components to be used and/or replaced instead of using ``CsrfMiddleware``. +.. versionchanged:: 1.1 + (previous versions of Django did not provide these two components + of ``CsrfMiddleware`` as described above) + .. _9.1.1 Safe Methods, HTTP 1.1, RFC 2616: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html Limitations |