[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. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9582 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
3594f322ed
commit
8479543fd7
|
@ -142,6 +142,13 @@ All attributes except ``session`` should be considered read-only.
|
|||
* ``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
|
||||
|
|
Loading…
Reference in New Issue