diff options
| author | Fabien Potencier <fabien.potencier@gmail.com> | 2012-07-06 15:59:17 +0200 |
|---|---|---|
| committer | Fabien Potencier <fabien.potencier@gmail.com> | 2012-07-06 15:59:19 +0200 |
| commit | b0257cd46a78251a25c17b91acb4dbbf6890590a (patch) | |
| tree | 1d2247c42353ce83d59f10d5f6c818d4a2d4b9a6 /Http/Authentication/AuthenticationSuccessHandlerInterface.php | |
| parent | 2f1d9c044819b56eb4b2fbba81ac2d5d46500bfb (diff) | |
| download | symfony-security-b0257cd46a78251a25c17b91acb4dbbf6890590a.zip symfony-security-b0257cd46a78251a25c17b91acb4dbbf6890590a.tar.gz symfony-security-b0257cd46a78251a25c17b91acb4dbbf6890590a.tar.bz2 | |
[Security] fixed automatic registration of the response listener when creating the listener
This is not a problem with Symfony, but when using the component
standalone (Silex for instance), the context listener might be
instantiated even if the firewall does not need to be fired. In that
case, the handle() method is not called, but the response listener is
called, which means that en empty token is stored in the session.
For Silex, it means that when authenticated, if you visit a 404 page,
you would be disconnected automatically.
Diffstat (limited to 'Http/Authentication/AuthenticationSuccessHandlerInterface.php')
0 files changed, 0 insertions, 0 deletions