Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

[1.3.X] Fixed #16430 - Stronger wording for CSRF protection in `modif…

…ying upload handlers on the fly`; thanks tomchristie.

Backport of r16588 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@16589 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 3e5fc7ebb1ebbaa2d6815b8e5b98d8c845012bca 1 parent 199f10f
Tim Graham authored

Showing 1 changed file with 6 additions and 6 deletions. Show diff stats Hide diff stats

  1. 12  docs/topics/http/file-uploads.txt
12  docs/topics/http/file-uploads.txt
@@ -278,13 +278,13 @@ list::
278 278
 
279 279
     Also, ``request.POST`` is accessed by
280 280
     :class:`~django.middleware.csrf.CsrfViewMiddleware` which is enabled by
281  
-    default. This means you will probably need to use
  281
+    default. This means you will need to use
282 282
     :func:`~django.views.decorators.csrf.csrf_exempt` on your view to allow you
283  
-    to change the upload handlers. Assuming you do need CSRF protection, you
284  
-    will then need to use :func:`~django.views.decorators.csrf.csrf_protect` on
285  
-    the function that actually processes the request.  Note that this means that
286  
-    the handlers may start receiving the file upload before the CSRF checks have
287  
-    been done. Example code:
  283
+    to change the upload handlers.  You will then need to use
  284
+    :func:`~django.views.decorators.csrf.csrf_protect` on the function that
  285
+    actually processes the request.  Note that this means that the handlers may
  286
+    start receiving the file upload before the CSRF checks have been done.
  287
+    Example code:
288 288
 
289 289
     .. code-block:: python
290 290
 

0 notes on commit 3e5fc7e

Please sign in to comment.
Something went wrong with that request. Please try again.