|
| > As Todd says, it could be a config sequencing issue.
I wouldn't think so, because there isn't much to configure in httpd.conf in
terms of priority / sequencing. I haven't tried placing WebSphere LoadModule
and WebSpherePluginConfig directives at different places in the config file,
but my experience is that the plugin catches all requests and decides if it
is to be served by a WebSphere app or by IHS (based on the plugin
configuration file). And, when FileServingEnabled attribute is set to false
(ibm-web-ext.xmi), the welcome-file-list directive is not taken into
account.
As an easy by-pass, we place an index.html to redirect to index.jsp (with
Javascript or <meta> directive). If there are many directories, it can
easily be scripted (with a shell script, for example).
I'd suppose one can also write a LocationMatch directive to do a Redirect.
Or maybe use mod_rewrite to make the request look like it was for index.jsp.
But I haven't experienced with these latter two solutions though.
|
|