#1084: turbogears.redirect fails if the tg app is deployed behind a proxy or
rewrite mechanism
----------------------+-----------------------------------------------------
Reporter: jtate | Owner: anonymous
Type: defect | Status: new
Priority: highest | Milestone: 1.0
Component: CherryPy | Version: 0.9a6
Severity: normal | Keywords:
----------------------+-----------------------------------------------------
If you set up a method which *just* redirects, i.e.
http://externalhost.example.com/testredir, and your tg app is running at
http://localhost:8080/, your redirect will be to
http://localhost:8080/redirtarget, which if run from another system will
give you a 404 at best, and most likely a could not connect to host error.
splee said that he would look into this tomorrow, but this should be
considered a blocker for 1.0.
Note that this problem is most noticeable when using the identity
framework; after a successful login, a redirect occurs and the new host is
sent, canceling out the session cookie already established.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/1084>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
