so the workaround i came up with is to have my own additional config setting specifying the hostname for the application and then not using tg.url directly, but prepending the host in my own "url" utility function. the remaining question: did i exploit unintended behaviour before, or can i expect full URLs to work as prefix in tg 2.1 final? best regards, robert
On Fri, Nov 6, 2009 at 10:49 AM, Robert Forkel <[email protected]> wrote: > hm, > full URLs seem to be no longer ok as prefix, so > > prefix = /wals > > works. But I really need full absolute URLs returned from tg.url(). > Any ideas how this may be achieved? > regards, > robert > > On Fri, Nov 6, 2009 at 10:38 AM, Robert Forkel <[email protected]> > wrote: >> >> hi all, >> still working on upgrading an app from tg 2.0.3 to tg 2.1a2. >> The application should be deployed behind apache as proxy, and i was >> using the following configuration with tg 2.0.3: >> >> [filter:proxy-prefix] >> use = egg:PasteDeploy#prefix >> prefix = http://localhost/wals >> >> [app:main] >> use = egg:wals >> full_stack = false >> filter-with = proxy-prefix >> >> after the upgrade to tg 2.1a2, i only get 404 for all URLs. >> Has anyone else encountered this behaviour - and maybe found >> workarounds? >> best regards, >> robert >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
