[1.3.X] Fixes #16532 -- Clearer explanation of how the test client expects HTTP headers to be passed. Thanks for the patch, Ricardo Bánffy.
Backport of r16554 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@16555 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
2a1874521e
commit
41e086cfb5
|
@ -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::
|
||||
|
|
Loading…
Reference in New Issue