Re: AliasMatch ^/(.*) /$1

Frank

As far as I know, this is weird - it has this effect -

The regular expression that defines the match is (.*) - this means any character (the dot) repeated (the asterisk) will be saved as a value that can be used later in the expression (the parentheses) and it is the first one, so that replacement marker will be $1.

The caret means the end of the URL including port, maybe - actually the beginning of what follows that - weird way to describe - sorry.

So this means that if you put the word home at the end of a URL, as here -

http://some.url.com:port/home

it will try to work with things in the

/home

directory in the IFS.

But then you either need a container (<directory> directive) for either the root of the IFS or for the home directory, to define access to contents of that directory - but this is ultra generic - that's why I think it's weird. Maybe even a security issue, but I'm not sure of that.

Is there also in the httpd.conf a <directory> entry that looks like

<directory />

and is there an "allow all" in there?

If so, it's a gaping hole, again, so far as I know!!

Now the web admin would NOT put this in on its own, that I know of.

That's all I know on a Monday.

HTH
Vern

On 1/28/2013 1:19 PM, fbocch2595@xxxxxxx wrote:

Hi Folks, I'm working with biz partners who are asking me how AliasMatch ^/(.*) /$1
got in /www/apache/conf/httpd.conf. I'm assuming that AliasMatch ^/(.*) /$1 was added by the OS (licpgm's?)...is that true? If anyone want to explain what the AliasMatch ^/(.*) /$1 statement is plz do but not necessary. We don't use alias names as far as I know since the server properties don't show AliasMatch ^/(.*) /$1 on any of the screens except as an example, when I view my servers via http://172.1.1.111:2001/HTTPAdmin
Is it typical to have /www/apache/conf/httpd.conf contain AliasMatch ^/(.*) /$1?

Thanks, Frank