PREPEND_WWW breaks the test client

[Andy Baker]

With PREPEND_WWW set to true the test client will always give a 301 status_code:

    >>> from django.test.client import Client
    >>> c = Client()
    >>> r = c.get('/admin/', follow=True)
    >>> r.status_code
    301
    >>> r.redirect_chain
    [('http://www.testserver/admin/', 301), ('http://www.testserver/admin/', 301)]

[Stavros Korokithakis]

+1, this behaviour serves no purpose. It only makes testing difficult and forces me to never use prepend_www and rather do my redirects at the webserver level. Perhaps PREPEND_WWW should be disabled before every test automatically, since it's not what testing is supposed to test for?

[Mark Lavin]

Added failing test case.

[Mark Lavin]

Not sure how to fix but I've added a test case which demonstrates the described issue.

[Sharpek]

I' going to check&fix this issue.

[James Beith]

I’ve been experiencing this and am using SERVER_NAME and host as a fix. Though as the number of tests I write for the project grows it doesn’t seem the most ideal solution.

response = self.client.get('/redirect/', follow=True, SERVER_NAME='www.testserver')
self.assertRedirects(response, '/result/', status_code=301, host='www.testserver')