Hi, I had a similar issue, and solved it after Anthony explained how _next works:
"When you attempt to access a protected URL and are not logged in, web2py redirects to the login page and puts the original URL in the _next variable, which results in a post-login redirect to the originally requested URL. auth.settings.login_next doesn't do anything if the login URL already contains a _next variable -- it only serves as a default post-login redirect in case the URL doesn't already contain a _next variable." I hope this answers your question as well. Annet -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.