Jan 25th, 2007, 02:13 PM
problems with Acegi and WebSphere 6.1
I've just run into a problem with a Spring/Acegi web app, trying to run it on a WebSphere 18.104.22.168 server. Basically, it appears that WebSphere v22.214.171.124 (and at least v.126.96.36.199) has a bug that generates a 404 error instead of invoking filters on URI requests that aren't actually present in the web app.
This means that /myapp/j_acegi_security_check returns a 404 instead invoking ANY of the filters for the app (including ones with URI patterns like /*). So Acegi doesn't appear to function with 188.8.131.52/5, which are the versions that I've actually tried.
This issue is similar to IBM bug PK27620, http://www-1.ibm.com/support/docview...id=swg1PK27620, which describes the same filter issue, only specifically with JSP resources. That bug is supposed to have been fixed in v184.108.40.206.
It looks like the issue I describe is a variant of that problem. I have submitted a problem report to IBM.
Has anybody found a workaround to get Acegi working?
I'm using Acegi 1.0.2/3.