Fixed a few small rst errors in request/response and fastcgi docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3191 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2006-06-21 23:06:24 +00:00
parent a159f660fe
commit a490d6b4f6
2 changed files with 4 additions and 3 deletions

View File

@ -3,7 +3,7 @@ How to use Django with FastCGI
============================== ==============================
Although the current preferred setup for running Django is Apache_ with Although the current preferred setup for running Django is Apache_ with
`mod_python`_, many people use shared hosting, on which FastCGI_ is the only `mod_python`_, many people use shared hosting, on which FastCGI is the only
viable option. In some setups, FastCGI also allows better security -- and, viable option. In some setups, FastCGI also allows better security -- and,
possibly, better performance -- than mod_python. possibly, better performance -- than mod_python.

View File

@ -49,7 +49,8 @@ All attributes except ``session`` should be considered read-only.
It's possible that a request can come in via POST with an empty ``POST`` It's possible that a request can come in via POST with an empty ``POST``
dictionary -- if, say, a form is requested via the POST HTTP method but dictionary -- if, say, a form is requested via the POST HTTP method but
does not include form data. Therefore, you shouldn't use ``if request.POST`` does not include form data. Therefore, you shouldn't use ``if request.POST``
to check for use of the POST method; instead, check `method`_. to check for use of the POST method; instead, use ``if reuqest.method ==
"POST"`` (see above).
Note: ``POST`` does *not* include file-upload information. See ``FILES``. Note: ``POST`` does *not* include file-upload information. See ``FILES``.