On Sun, Jun 17, 2007 at 09:03:42PM -0000, Jose Figueras wrote: > > On 17 jun, 13:22, Christoph Haas <[EMAIL PROTECTED]> wrote: > > On Sun, Jun 17, 2007 at 10:01:24AM -0000, Jose Figueras wrote: > > > Following "Authkit with Pylons" article (and a mixture of other > > > articles, docs, etc) If I try to protect my whole application I see > > > this strange error: "exceptions.AssertionError: Forwarding loop > > > detected; '/signin' visited twice (internal redirect path: ['/public', > > > '/signin']) ". > > > > It usually means that your signin controller couldn't be accessed > > without authentication. If you enforce authentication everywhere there > > is no signin action you can even reach because you are not yet > > authenticated. Chicken, egg. Check that you can call /signin without > > problems first. > > It's possible to un-enforce authentication on one controller's method > (or one controller)?
I don't think so. You'll have to use authentication for all the methods except the "signin" form. My personal preference is to have a "login" controller that deals with authentication (login/logout). All the other controllers may enforce authentication. Perhaps you put too much application logic into that very controller that has nothing to do with the actual authentication? Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
