test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #9712 -- Documented how HTTP headers are converted to request.META keys. 

Based on a patch from masklinn.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@9579 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-12-07 03:41:54 +00:00
parent 84cc008473
commit 04ff1aff12
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/ref/request-response.txt
View File

@ -142,6 +142,13 @@ All attributes except ``session`` should be considered read-only.
* ``SERVER_NAME`` -- The hostname of the server. * ``SERVER_NAME`` -- The hostname of the server.
* ``SERVER_PORT`` -- The port 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 .. attribute:: HttpRequest.user
A ``django.contrib.auth.models.User`` object representing the currently A ``django.contrib.auth.models.User`` object representing the currently