#5592: HttpResponseRedirect dosen't work anymore with Squid Reverse Proxy
--------------------------------------------+-------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: reopened | Component: HTTP
handling
Version: SVN | Resolution:
Keywords: redirect reverse proxy squid | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------------+-------------------------------
Comment (by mtredinnick):
No, that doesn't give us more information about how to repeat the problem.
That just tells us what you changed to make it work with your particular
-- completely unknown to us -- installation.
What are the relevant Squid configuration lines for example? What is an
example of the HTTP response being sent across the wire that doesn't work?
As I mentioned above, we are now sending (or should be sending, barring
some minor bug) ''correct'' Location headers. So I strongly suspect a
configuration problem on your end somewhere. Try to capture the response
that is causing the problem (use wireshark or something similar, for
example). Try to replicate the problem in a small example. Print out the
value of !responseLocation that we construct to see what it looks like.
Any of this would be information we could use to debug the problem
further. Suggesting that we just remove the very line that fixes the bug
is not information that helps anybody debug further.
--
Ticket URL: <http://code.djangoproject.com/ticket/5592#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
