There is an application that works on WAS7. It has war module deployed on context path "Foo/Bar" (compound one). That is the war module is accessible via the URL like this: localhost:9080/Foo/Bar.
Then I deployed the same application on WAS 8.5.5. Trying to access war module with the same URL localhost:9080/Foo/Bar (without trailing slash) and getting the "bare" page without css and js files retrieved. However, when I try to access module via the following URL localhost:9080/Foo/Bar/ (with trailing slash) css and js get picked up correctly.
What I was able to figure out so far, is that on WAS 7 everything worked because there was redirect from URL with no trailing slash to URL with trailing slash. And it seems like it is normal behavior http://webdesign.about.com/od/beginningtutorials/f/why-urls-end-in-slash.htm. The question is why don't I have the same behavior on WAS 8.5.5 ? Is there any way to configure it?