From 4f50d248a888f04f3ba93b04aaf40aa65a7d5fee Mon Sep 17 00:00:00 2001 From: Chris Beaven Date: Thu, 28 Jul 2011 22:09:26 +0000 Subject: [PATCH] =?UTF-8?q?Fixes=20#16532=20--=20Clearer=20explanation=20o?= =?UTF-8?q?f=20how=20the=20test=20client=20expects=20HTTP=20headers=20to?= =?UTF-8?q?=20be=20passed.=20Thanks=20for=20the=20patch,=20Ricardo=20B?= =?UTF-8?q?=C3=A1nffy.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit git-svn-id: http://code.djangoproject.com/svn/django/trunk@16554 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/testing.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index 6595c51957..2362193960 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -710,6 +710,15 @@ arguments at time of construction: details view, which is a good way to test code paths that use the :meth:`django.http.HttpRequest.is_ajax()` method. + .. admonition:: CGI specification + + The headers sent via ``**extra`` should follow CGI_ specification. + For example, emulating a different "Host" header as sent in the + HTTP request from the browser to the server should be passed + as ``HTTP_HOST``. + + .. _CGI: http://www.w3.org/CGI/ + If you already have the GET arguments in URL-encoded form, you can use that encoding instead of using the data argument. For example, the previous GET request could also be posed as::