On Sun, 2011-12-11 at 09:13 -0800, Mike Orr wrote: > On Sat, Dec 10, 2011 at 10:48 PM, Chris McDonough <[email protected]> wrote: > > On Sat, 2011-12-10 at 22:39 -0800, rihad wrote: > >> Sorry if a bit irrelevant. The changelog says: "The SQLAlchemy + URL > >> Dispatch Wiki Tutorial has been updated.". But what I believe to be a > >> bug that I mentioned here: > >> http://groups.google.com/group/pylons-devel/browse_thread/thread/d81a2d98cb64dd6b > >> has remained seemingly unnoticed. > > > > Neither thing you mention there seems to be a bug. The line: > > > > url = request.application_url + '/login' > > > > Is constructed for the benefit of the template, which uses it as a form > > post target. It can't be url = request.url, as the current URL when the > > login view is invoked may not be the login form. > > The default templates to mix API styles. That seems to be a feature > rather than a bug because it shows different ways of doing things. But > is the above better in any practical way than > request.route_url("login") > which Pylons users have been told to prefer? Or is it just as good either way?
It should probably use route_url. > Also, do the *_url methods work correctly behind mod_proxy, where the > URL of the WSGI server is not something you can make a valid link to. Yes. - C -- 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.
