| Author |
location tag conflicts
|
|
| danto2@volcanomail.com 2006-10-26, 7:18 am |
| We are running Apache 2.0.59 on Solaris 8 and we have a virtual file
with multiple location tags. Each of these tags is configured to use
the BEA weblogic plug-in to route requests to weblogic (v 8.1.5).
We are having problems with conflicts between location tag names and
the names of the files we are trying to serve which results in Apache
returning a 404 error.
For example if we have location tags like:
<Location /bread>
SetHandler weblogic-handler
WeblogicCluster weblogicserver:8001
....
</Location>
<Location /cheese>
SetHandler weblogic-handler
WeblogicCluster weblogicserver:9001
....
</Location>
And we then try and serve this file:
http://www.xxx.com/bread/stuff/cheese_1.gif.
My understanding is that Apache should route this request to the /bread
location on port 8001 of the weblogic server. Instead it routes the
request to the /cheese location on port 9001 and ends up with a 404.
This happens when we try and serve any file whose name or path includes
a location tag name.
Does anyone have any insight into this behaviour?
Thanks!
| |
| shimmyshack 2006-10-26, 1:16 pm |
|
depending on your setup you could start using LocationMatch instead
<LocationMatch ^/bread>
<LocationMatch ^/cheese>
here you are able to specify that / will be the first character of the
match
| |
| danto2@volcanomail.com 2006-10-26, 1:16 pm |
| shimmyshack wrote:
> depending on your setup you could start using LocationMatch instead
> <LocationMatch ^/bread>
> <LocationMatch ^/cheese>
> here you are able to specify that / will be the first character of the
> match
Thanks very much for this, it makes a lot of sense. We need to do more
testing but its certainly pointed us in the right direction and so far
appears to have resolved the issue.
|
|
|
|