#5592: HttpResponseRedirect dosen't work anymore with Squid Reverse Proxy
--------------------------------------------+-------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: HTTP
handling
Version: SVN | Resolution: invalid
Keywords: redirect reverse proxy squid | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------+-------------------------------
Changes (by mtredinnick):
* status: reopened => closed
* resolution: => invalid
Comment:
So this is a configuration error on your side and the Squid error message
is telling you exactly what the problem is. The domain name must be valid.
Django builds up the domain name from these HTTP headers (in this order;
the first one present is the hostname):
1. The "X-Forwarded-Host" HTTP header
2. The "Host" HTTP header (Required in all HTTP/1.1 requests)
3. The server name (if using the mod_python handler)
Somewhere (and I guess it's the ServerName directive in you Apache
config), you're setting the name to backendpool. You have to fix that to
make it something Squid can resolve.
This is not a Django bug.
--
Ticket URL: <http://code.djangoproject.com/ticket/5592#comment:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
