Your proposal does not work if the user access part of the website not secured. In that case, only the filter can logon the user automatically.
On May 2, 3:02 pm, Vojto <[email protected]> wrote: > Hello, > > why sfGuardPlugin use filter for remember functionality? > > Wouldn't it make much more sense if cookie check took place somewhere > in login action? > > Imagine this flow: > > 1. User opens a secured page > 2. User gets redirected to login action of sfGuardPlugin > 3. login action first checks for "remember me" cookie, if there's not > one, it will display login form > > ... > > What do you people think? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
