Malcolm Tredinnick 3ee3d6b5f3 Fixed #5898 -- Changed a few response processing paths to make things harder to get wrong and easier to get right. Previous behaviour wasn't buggy, but it was harder to use than necessary. ... We now have automatic HEAD processing always (previously required ConditionalGetMiddleware), middleware benefits from the Location header rewrite, so they can use relative URLs as well, and responses with response codes 1xx, 204 or 304 will always have their content removed, in accordance with the HTTP spec (so it's much harder to indavertently deliver invalid responses). Based on a patch and diagnosis from regexbot@gmail.com. git-svn-id: http://code.djangoproject.com/svn/django/trunk@6662 bcc190cf-cafb-0310-a4f2-bffc1f526a37		2007-11-11 03:55:44 +00:00
..
__init__.py	Fixes #2333 -- Added test fixtures framework.	2007-03-01 13:11:08 +00:00
_doctest.py	Fixed #5442 -- Added Jython workaround in django.test._doctest. Thanks, leo.soto@gmail.com	2007-09-14 17:17:37 +00:00
client.py	Fixed #5898 -- Changed a few response processing paths to make things harder to get wrong and easier to get right. Previous behaviour wasn't buggy, but it was harder to use than necessary.	2007-11-11 03:55:44 +00:00
signals.py	Refs #2333 - Re-added the template rendering signal for testing purposes; however, the signal is not available during normal operation. It is only added as part of an instrumentation step that occurs during test framework setup. Previous attempt (r3659) was reverted (r3666) due to performance concerns.	2006-09-02 09:26:24 +00:00
simple.py	Fixed #4460 -- Added the ability to be more specific in the test cases that are executed. This is a backwards incompatible change for any user with a custom test runner. See the wiki for details.	2007-07-28 04:02:52 +00:00
testcases.py	When using assertRedirect(), allow the caller to specify relative URLs and	2007-11-11 03:54:21 +00:00
utils.py	Modified the test harness to respect the LANGUAGE_CODE setting. Also changed	2007-10-21 17:26:32 +00:00