httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Slive" <>
Subject Re: [users@httpd] Help with Apache <Location> directive
Date Tue, 02 Oct 2007 00:34:41 GMT
On 10/1/07, <> wrote:
> Joshua,
> Thanks for your suggestion.
> > Use <LocationMatch ^/xfer$>
> Does this mean any URL that has /xfer should be passed along by the
> Location directive. But i do not see that happening.
> The example that i gave was a bit off from my actual problem, where the
> request coming in is
> To handle this request, i attempted to use <LocationMatch ^/xfer/xfer$>
> but apache did not recognize the incoming URL as matching this and rejected
> the request. I am not very fluent in Regex, what am i missing here?

The regex above matches only the exact string /xfer with nothing
before or after. To match your request, you need something like
<LocationMatch ^/xfer/xfer/Servlet$>. But note this will work only for
that SINGLE url. You'll need to design a regex that matches all urls
that should be going to that server.

> > But note also that in most cases, later <Location> sections will
> > override earlier ones. So there is likely also a problem with whatever
> > module you are using to impliment "send to server", since it isn't
> > respecting apache config precendence rules.
> I am using the WebLogic plugin module. If i understand you right what you
> are saying is that if the request coming in has the format
> /xfer/xfer/1/Servlet, even
> if there is a directive with "/xfer/xfer" earlier in the Location list, it
> should be overriden by "/xfer/xfer/1" since it is later in the Locations
> list.
> I did not realize that there was a Locations precedence list based on its
> position within the conf file.

Yes, later <Location> sections override earlier ones. See:


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message