diff options
| author | Ramiro Morales <cramm0@gmail.com> | 2014-06-25 12:15:20 -0300 |
|---|---|---|
| committer | Ramiro Morales <cramm0@gmail.com> | 2014-06-25 12:15:20 -0300 |
| commit | 77c0a904cbb2ff144dc42deac4e9fbca0c370f1b (patch) | |
| tree | c69822b402e36d29181bf884c98c19d8d8dab853 | |
| parent | e0cd07ec2f394e6db3d17de19809a8f377cd1578 (diff) | |
Fixed typo in revamped forms intro doc.
| -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 a8730871e5..8f7d25ddcb 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, |