You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem's not in the Filter code but rather WebSphere changed the way they
handle
servet filters after 6.1.0.5, if there's no file extension or a static file
extension
the Servlet Filter just won't be invoked at all, which typically results in a
404.
These instructions for the WebSphere community will get the filters to behave
as they
did before:
In the WebSphere Admin Console:
- expand Servers -> Application Servers -> <server> -> Web Container Settings
-> Web
Container -> Custom Properties
- select New and then enter
"com.ibm.ws.webcontainer.invokefilterscompatibility" as
the property name and "true" as the value
- save the update and restart the server
Original comment by 911c...@gmail.com on 21 Mar 2008 at 8:45
Original issue reported on code.google.com by
jinqing...@gmail.com
on 29 Oct 2007 at 12:52The text was updated successfully, but these errors were encountered: