On Mon, 2009-08-31 at 22:53 -0700, Mike Orr wrote: > On Mon, Aug 31, 2009 at 10:14 PM, Iain Duncan<[email protected]> wrote: > > > > Hey folks, I'm trying to call a repoze.bfg app as a wsgi app from > > pylons. bfg app provides a wsgi callable, so I made a controller in > > pylons called 'admin'. > > > > in routing.py I have: > > > > map.connect('/admin', controller='admin') > > > > > > and in admin.py I have: > > > > from dram.run import app > > AdminController = app() > > > > My bfg app is getting called ok, but to it path is > > still /admin/other/stuff/here. I would have thought that if we are > > mapping the route to a wsgi app, the part used up in the mapping would > > be stripped out as part of the prepping of the wsgi environment, but I > > guess that doesn't happen in this scenario. Can anyone tell me what the > > crustimony proceedcake is for calling wsgi apps from pylons with the > > environment altered such that the called app acts like it's getting a > > regular request? > > map.connect("/admin/{path_info:.*}", controller="admin")
Hi Mike and others, I just tried that and the wsgi callable still gets an altereded evn. Path info is '/admin' and script name is still ''. Any ideas what might have gone wrong? or other ways to accomplish this? thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
