From 9dc9770736ddf236be5ae08447bb323433fffd44 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Tue, 27 Oct 2009 21:52:25 +0000 Subject: Documented the presence of {% csrf_token %} in Django 1.1.2 in trunk docs. git-svn-id: http://code.djangoproject.com/svn/django/trunk@11675 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/templates/builtins.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'docs/ref/templates') diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt index 7084dc0a78..8266224c39 100644 --- a/docs/ref/templates/builtins.txt +++ b/docs/ref/templates/builtins.txt @@ -56,9 +56,12 @@ Ignore everything between ``{% comment %}`` and ``{% endcomment %}`` csrf_token ~~~~~~~~~~ -.. versionadded:: 1.2 +.. versionadded:: 1.1.2 -This is described in the documentation for :ref:`Cross Site Request Forgeries `. +In the Django 1.1.X series, this is a no-op tag that returns an empty string for +future compatibility purposes. In Django 1.2 and later, it is used for CSRF +protection, as described in the documentation for :ref:`Cross Site Request +Forgeries `. cycle ~~~~~ -- cgit v1.3