Re: Cleaning up old bugs

One enhancement I've used locally, is to check for 401 codes after the  
filter has run. This is done using a response wrapper in addition to  
the request wrapper, and some extra logic in the SecurityFilter class.

This allows us to have a subsystem return a 401, and security filter  
automatically redirecting to the login screen. It makes it much easier  
to have dynamic permissions, since it's no longer declared statically  
in the security filter configuration file.

This might be handy for someone else as well?

-- 
Torgeir Veimo
[email protected]




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/