summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Plant <L.Plant.98@cantab.net>2011-06-14 23:31:45 +0000
committerLuke Plant <L.Plant.98@cantab.net>2011-06-14 23:31:45 +0000
commit06a2515145d8a5e6ee67da1f1849f157e23c6578 (patch)
tree1e063a11e8ba699be91cac2cba28d0e308d9cd7e
parent3f37d1673bb8826e1648f77143b94356c5886e16 (diff)
Fixed typo in release notes regarding CSRF with PUT/DELETE etc
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16401 bcc190cf-cafb-0310-a4f2-bffc1f526a37
-rw-r--r--docs/releases/1.4.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index cc20795ded..1ad6092612 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -340,7 +340,7 @@ Previously, Django's :doc:`CSRF protection </ref/contrib/csrf/>` provided
protection against only POST requests. Since use of PUT and DELETE methods in
AJAX applications is becoming more common, we now protect all methods not
defined as safe by RFC 2616 i.e. we exempt GET, HEAD, OPTIONS and TRACE, and
-enforce protection on everything.
+enforce protection on everything else.
If you using PUT or DELETE methods in AJAX applications, please see the
:ref:`instructions about using AJAX and CSRF <csrf-ajax>`.