On 7/13/05, Kvetch <kvetch@xxxxxxxxx> wrote:
> I tested it on Apache2.0.49 and it does allow me to use the same Alias for
> mutlple virtual hosts that point to different locations. So is this new in
> 2.0.54?
>
> On 7/13/05, Kvetch <kvetch@xxxxxxxxx> wrote:
> > Hello, I just upgraded from Apache 2.0.49 to Apache 2.0.54. I have a ton
> of virtual hosts in my conf and now when I start Apache I get a million
> warning messages stating
> > [warn] The Alias directive in
> /usr/local/apache2.0.54/conf/httpd.conf at line 3267 will
> probably never match because it overlaps an earlier Alias.
> >
> > My questions are - is this warning new because I can put my 2.0.49 conf in
> the 2.0.54 install and still get the warnings. Did these overlapping
> Aliases ever work? I am guessing they did not but Apache 2.0.49 didn't warn
> me about it. Is this a new warning in the 2.05x versions? Is there a way
> to get an overlapping Alias to work in a VHost with a different domain name?
> If I have domain A with an Alias /test to /01/test1 and then domain B with
> an Alias /test /01/test2, does domain B's Alias to /test go to /01/test?
Yes, the warning is new but the behavior of the Alias has not changed.
But this warning should not be triggered for overlapping aliases in
different vhosts. It is only when the Aliases overlap in the same
context.
Joshua.
|