Ben_ wrote: 
>
> I wouldn't think so, because there isn't much to configure in httpd.conf i
n
> terms of priority / sequencing. I haven't tried placing WebSphere LoadModu
le
> and WebSpherePluginConfig directives at different places in the config fil
e,
> but my experience is that the plugin catches all requests and decides if i
t
> is to be served by a WebSphere app or by IHS (based on the plugin
> configuration file). And, when FileServingEnabled attribute is set to fals
e
> (ibm-web-ext.xmi), the welcome-file-list directive is not taken into
> account.

That's my impression of how the plugin works, too, but I only have
experience with 3.5. But I think there are other things you can fiddle
in the httpd.conf that will interfere with the request getting to the
plugin like virtual hosting and such. I could be all wet, too.

> 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.js
p.
> But I haven't experienced with these latter two solutions though.

We've done both straight <meta> refresh and Javascript multi-root
redirects to handle similar situations.

[ Post a follow-up to this message ]