On Wed, Jul 9, 2008 at 12:47 AM, Diez B. Roggisch <[EMAIL PROTECTED]> wrote: > > Jorge Godoy schrieb: >> On Tuesday 08 July 2008 21:51:49 [EMAIL PROTECTED] wrote: >>> Yeah...I believe you. >>> >>> But I still can't get it to work. >>> >>> And this seems to. :) >>> >>> I'd rather spend my time modifying python code, then trying to debug >>> apache. >> >> That's up to you. >> >> Anyway, if I were you, I'd never edit the code in TG for doing that. I would >> either create a new version of redirect inside the project -- or as a module >> -- or (better yet) I would monkey patch TG's code. >> >> If you edit TG's code you will have to remember doing that on every >> installation and every update. If you monkey patch then it is all in your >> code and whenever you install it, it will simply work. >> >> This is the recommended approach for any Python project. > > I'm not deep enough into the subject to judge if the enhancement is > worth being added to TG itself to ease apache-deployment. > > However, I can only *strongly* support Jorge's above remarks! I happen > to have to maintain a TG 1 project that I back then based on a heavily > patched TG version. And now moving it to TG1.0.X gives me headaches. > > Better try & keep your changes inside your project, and monkey-patch if > needed. >
Does this redirection problem for https happens on both setups? ProxyPassReservers and mod_Wsgi? Lucas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
