Looking to pass a "root" request to a WL server with Apache plugin

Question

Anyone know of a way to disclude a URL from the <Location> directive? I'm
using the Apache plugin and would like to pass all requests through to the
WL server except the images (which can be identified either by extension or
by location (/images)). I want a request for http://apacheserver/ to get
passed to the WL server and execute some default servlet. However... if I
use <Location /> to pass this through... everything else will get passed
through, even my image requests.
Any ideas?

Answer 1

Thanks for the help.
Two location directives:
<Location /myApp> and
<Location /myImages>
would end up passing my images request through to WL, no?
The way I have it set up now, I have one tag:
<Location /myApp>
which (obviously) passes the /myApp/* requests to WL. This is good...
any other request such as /images/myimage.gif stays on the web server. The
only problem is that
the initial hit to the site (www.mycompany.com) does not get passed through
and
I need it to map to a servlet on the WL server, without disrupting the flow
of a
/images/* request.. I have no images on the WL server.
Anyone know of a way to disclude a URL from the <Location> directive?I'm
using the Apache plugin and would like to pass all requests through tothe
WL server except the images (which can be identified either by extensionor
by location (/images)). I want a request for http://apacheserver/ to
get
passed to the WL server and execute some default servlet. However... ifI
use <Location /> to pass this through... everything else will get passed
through, even my image requests.
Have your application reside at /myApp and images in /myImages. Then two
<Location> stanzas,
one for /myApp and one for /myImages will do what you want. I have an
open case with support
where I wanted /myApp/myImages and /myApp to resolve in the order the
<Location> directives
were found in httpd.conf, in much the same way you can have / and
/images with
Apache handling /images and WLS handing / . The case is still open and
the workaround is
described in the first sentence of this paragraph :)