Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

urlrewritefilter does not work in websphere 6.1, but work well in websphere 6.0.2.x #6

Closed
GoogleCodeExporter opened this issue Mar 17, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

urlrewritefilter does not work in websphere 6.1, but work well in 
websphere 6.0.2.x

Original issue reported on code.google.com by jinqing...@gmail.com on 29 Oct 2007 at 12:52

@GoogleCodeExporter
Copy link
Author

Can you give any more information about what exactly isn't working? Since 
WebSphere
6.1 is a proprietary product, it is not easy for us to test this.

Original comment by mdillon....@gmail.com on 9 Nov 2007 at 3:36

@GoogleCodeExporter
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

Closing, nothing to do here.

Original comment by tuc...@gmail.com on 31 Jul 2008 at 10:38

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant