Author: mtredinnick
Date: 2011-08-21 21:27:36 -0700 (Sun, 21 Aug 2011)
New Revision: 16644
Modified:
django/trunk/docs/ref/request-response.txt
Log:
Improved documentation around HTTP server meta variables.
Fixed #16581, with thanks to Bernhard Essl.
Modified: django/trunk/docs/ref/request-response.txt
===================================================================
--- django/trunk/docs/ref/request-response.txt 2011-08-22 03:37:37 UTC (rev
16643)
+++ django/trunk/docs/ref/request-response.txt 2011-08-22 04:27:36 UTC (rev
16644)
@@ -125,10 +125,10 @@
Available headers depend on the client and server, but here are some
examples:
- * ``CONTENT_LENGTH``
- * ``CONTENT_TYPE``
- * ``HTTP_ACCEPT_ENCODING``
- * ``HTTP_ACCEPT_LANGUAGE``
+ * ``CONTENT_LENGTH`` -- the length of the request body (as a string).
+ * ``CONTENT_TYPE`` -- the MIME type of the request body.
+ * ``HTTP_ACCEPT_ENCODING`` -- Acceptable encodings for the response.
+ * ``HTTP_ACCEPT_LANGUAGE`` -- Acceptable languages for the response.
* ``HTTP_HOST`` -- The HTTP Host header sent by the client.
* ``HTTP_REFERER`` -- The referring page, if any.
* ``HTTP_USER_AGENT`` -- The client's user-agent string.
@@ -138,7 +138,7 @@
* ``REMOTE_USER`` -- The user authenticated by the Web server, if any.
* ``REQUEST_METHOD`` -- A string such as ``"GET"`` or ``"POST"``.
* ``SERVER_NAME`` -- The hostname of the server.
- * ``SERVER_PORT`` -- The port of the server.
+ * ``SERVER_PORT`` -- The port of the server (as a string).
With the exception of ``CONTENT_LENGTH`` and ``CONTENT_TYPE``, as given
above, any HTTP headers in the request are converted to ``META`` keys by
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
