Listeners priorities exceeds maximum value about nelmiosecuritybundle HOT 3 CLOSED

The main reason is that this bundle existed before the 255/-255 guidelines were in place. Back then as I recall the priorities varied greatly so we picked up very high numbers to make sure we act first since this is really basic http-level behavior that should occur before any framework code is executed. I am not sure if lowering them to 255 would cause issues or not, but I'd rather not change things that work.

from nelmiosecuritybundle.

I understand, it would be very hard to make sure you are the first to be fired if you picked 255 as the priority since Symfony has a lot of events firing at that priority. The only way to do it is to actually ignore the guidelines. Even the Symfony Profiler has a priority of 1024 to make sure it comes first. Thanks for clearing that up, it's more an issue with the guidelines and how the Symfony core uses event priorities.

from nelmiosecuritybundle.

OK, well no worries. Closing this then :)

from nelmiosecuritybundle.