From 04ff1aff12b2603c055d50daa4649754eb995e0a Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Sun, 7 Dec 2008 03:41:54 +0000 Subject: [PATCH] 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 --- docs/ref/request-response.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt index 18b8f665a53..fcf45232183 100644 --- a/docs/ref/request-response.txt +++ b/docs/ref/request-response.txt @@ -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