Author: mtredinnick
Date: 2008-12-06 21:49:06 -0600 (Sat, 06 Dec 2008)
New Revision: 9582
Modified:
django/branches/releases/1.0.X/docs/ref/request-response.txt
Log:
[1.0.X] Fixed #9712 -- Documented how HTTP headers are converted to
request.META keys. Based on a patch from masklinn.
Backport of r9579 from trunk.
Modified: django/branches/releases/1.0.X/docs/ref/request-response.txt
===================================================================
--- django/branches/releases/1.0.X/docs/ref/request-response.txt
2008-12-07 03:48:39 UTC (rev 9581)
+++ django/branches/releases/1.0.X/docs/ref/request-response.txt
2008-12-07 03:49:06 UTC (rev 9582)
@@ -142,6 +142,13 @@
* ``SERVER_NAME`` -- The hostname of the server.
* ``SERVER_PORT`` -- The port of the server.
+ With the exception of ``CONTENT_LENGTH`` and ``CONTENT_TYPE``, as given
+ above, any HTTP headers in the request are converted to ``META`` keys by
+ converting all characters to uppercase, replacing any hyphens with
+ underscores and adding an ``HTTP_`` prefix to the name. So, for example, a
+ header called ``X-Bender`` would be mapped to the ``META`` key
+ ``HTTP_X_BENDER``.
+
.. attribute:: HttpRequest.user
A ``django.contrib.auth.models.User`` object representing the currently
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
