tg controllers get the information about which method to call from routes, so if that info is wrong, we'd go to the wrong place.
Can you let me know what's in the routes environment variables when you get redirected to the wrong location? On Thu, Sep 11, 2008 at 1:10 PM, GustaV <[EMAIL PROTECTED]> wrote: > > I have no html template since I use GWT instead. > Anyway it is not about finding the login method (tg2 uses something > called repoze.who and do not manage login itself) but about the > redirection implied by the (default) login procedure. Actually the > same could potentially happen everywhere a redirect is raised outside > tg's controllers. > > On Sep 11, 3:32 pm, "Lukasz Szybalski" <[EMAIL PROTECTED]> wrote: >> On Thu, Sep 11, 2008 at 6:12 AM, GustaV <[EMAIL PROTECTED]> wrote: >> >> > Thanks for the explaination, I missed that. :) >> >> > Did you find any clue then? >> >> > On Sep 10, 5:13 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote: >> >> HTTPFound is a python exception, but also a WSGI response object. >> >> >> In general, we're not catching HTTPExceptions, but are instead passing >> >> them back up the wsgi stack in case some middleware handles them. >> >> >> On Wed, Sep 10, 2008 at 4:50 AM, GustaV <[EMAIL PROTECTED]> wrote: >> >> >> > I looked into it yesterday. >> >> > Everywhere I looked, SCRIPT_NAME was set properly : in the >> >> > repoze.who.plugin challenge method, in the configuration.py in tg, and >> >> > a lot or places. >> >> > It looks like it works when I do "raise HTTPFound" in a controller, >> >> > but not really when the who.plugin simply changes the app to HTTPFound >> >> > for example. I did not manage to find where the HTTPFound (exception >> >> > or application) was handled to check this. >> >> >> > On Sep 10, 7:27 am, "Mark Ramm" <[EMAIL PROTECTED]> wrote: >> >> >> Hmm, I haven't tested this, but is SCRIPT_NAME being set properly in >> >> >> your wsgi environ? >> >> >> >> I'm guessing that it is, but that there's some redirect code that's >> >> >> not paying attention to SCRIPT_NAME, and generating an absolute URL >> >> >> improperly. >> >> >> >> On Thu, Sep 4, 2008 at 4:57 PM, GustaV <[EMAIL PROTECTED]> wrote: >> >> >> >> > Hi all! >> >> >> >> > I'm experiencing some unpleasant issue in redirection. >> >> >> >> > I serve my app with apache 2.2 + mod_wsgi locally. I access it via : >> >> >> >http://localhost/seed >> >> >> >> > Apache httpd.conf : >> >> >> > WSGIScriptAlias /seed D:/Sandbox/Repo/SeedServer/apache/seed.wsgi >> >> >> > <Directory D:/Sandbox/Repo/SeedServer/apache> >> >> >> > Order deny,allow >> >> >> > Allow from all >> >> >> > </Directory> >> >> >> >> > Typing :http://localhost/seed/logout_handlerredirectsmeto >> >> >> >http://localhost/login, instead ofhttp://localhost/seed/login! >> >> >> >> > I tried to add in my prod.ini : >> >> >> > "filter-with = proxy-prefix" >> >> >> > and later: >> >> >> > [filter:proxy-prefix] >> >> >> > "use = egg:PasteDeploy#prefix >> >> >> > prefix = /seed" >> >> >> > (found >> >> >> > inhttp://turbogears.org/2.0/docs/main/Deployment/ModProxy.html) >> >> >> > but that doesn't change anything... >> >> >> >> > What happens here? >> >> ( = "login_result", not "seed/login_result") >> >> Can you look at the html template and see what link it has in there? >> I know in tg1 at one point there was a link to either login or logout >> that was just /logout instead of tg.url('/logout') >> >> Lucas > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
