diff options
| author | Ramiro Morales <cramm0@gmail.com> | 2014-06-25 12:15:20 -0300 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-06-25 12:32:14 -0400 |
| commit | 54a6ab207762bf581bf74e7e3d6b9e0520864baa (patch) | |
| tree | e1867468356c4c2481a007087947723b900e1082 /docs | |
| parent | f1428dc796817a241d49319122663129d78ca853 (diff) | |
[1.7.x] Fixed typo in revamped forms intro doc.
Backport of 77c0a904cb from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/forms/index.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index 054cb19deb..021bdd2ff1 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -80,7 +80,7 @@ all in plaintext. Neither would it be suitable for large quantities of data, or for binary data, such as an image. A web application that uses ``GET`` requests for admin forms is a security risk: it can be easy for an attacker to mimic a form's request to gain access to sensitive parts of the system. -``POST``, coupled with other protections like Django's:doc:`CSRF protection +``POST``, coupled with other protections like Django's :doc:`CSRF protection </ref/contrib/csrf/>` offers more control over access. On the other hand, ``GET`` is suitable for things like a web search form, |