Le 12/05/2011 00:19, ryan weaver a écrit :
* Due to the onCoreRequest ordering, you'll hit a 404 page before the
firewall forces authentication. How *big* of a deal is this? I'm not
used to this behavior, but the authentication listeners rely on being
*after* the onCoreRequest listener of the framework (for the session)
A solution could be to split the logic in 2 listeners. One responsible
to initialize the session, and the other responsible to do the routing.
And so the firewall could be registered between them.
Thus, registering the first one with a positive priority will ensure it
is called before any listeners registered the default way. This would
make the session available to the other onCoreRequest listeners without
relying on FrameworkBundle being registered first in the kernel (as the
order should not matter according to the decision made when refactoring
the bundle management).
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
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
