It is unfortunate that the TurboGears root controller path must be set to match the Apache proxied path. I class this as a work-around to a problem that is not yet solved. It should be possible to develop a TG app without using Apache (ie: direct to http://localhost:8080/) then deploy it behind an Apache (or any) proxy irrelevant of path. The proxy path should be changeable, with only config file modifications necessary. This simply relies on TG/CP handling relative URLs properly and constructing absolute URLs with the proxied base path taken into consideration.
TG/CP is 90% there with server.webpath and base_url_filter but the lack of support by redirect seems to be the only remaining issue that I can see. Also see Zope's VirtualHostMonster for an interesting implementation of this idea. Cheers, Chris On Nov 8, 7:57 am, Matthew Bevan <[EMAIL PROTECTED]> wrote: > To make sure relative redirects work, ensure that Apache is > redirecting to the correct base path. I had mine redirecting / > booking/* tohttp://localhost:8080/*which was causing lots of > problems. The correct path should have beenhttp://localhost:8080/ > booking/* --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
