dhainlin
Aug 8th, 2006, 11:40 AM
Don't know if this is a bug but it sure is a non intuitive feature...
When using the AntPathmatcher in our enforcement filter, we had
*.html** = ROLE_SOMETHING
This failed to match a url that looked like
/search.html?param=value¶m2=http://host/url¶m3=value
What we had to do to get it to work was
*.html**/**
Seems like this fools the path matcher enough to work.
This seems like a bug if the ** behavior is supposed to mean any path going forward...
Just wanted to put this out there...
When using the AntPathmatcher in our enforcement filter, we had
*.html** = ROLE_SOMETHING
This failed to match a url that looked like
/search.html?param=value¶m2=http://host/url¶m3=value
What we had to do to get it to work was
*.html**/**
Seems like this fools the path matcher enough to work.
This seems like a bug if the ** behavior is supposed to mean any path going forward...
Just wanted to put this out there...