Web Hosting Talk : Web Hosting Main Forums : Dedicated Server : AliasMatch ^/sites/([^/]+)(/(.*))? /home/sites/$1/web/$3

[Nology]

Anyone managed to get this to work on a RaQ 550 after adding it to httpd.conf?

AliasMatch ^/sites/([^/]+)(/(.*))? /home/sites/$1/web/$3

All I get is either a 'File Not Found' or 'Forbidden' when I go to:
http://www.mydomain.com/sites/www.clientdomain.com

Any ideas?

[mlegler]

this won't ever work, I guess, because you're trying to walk outside (above) the DocumentRoot of mydomain.com, /home/sites/www.clientdomain.com isn't underneath /home/sites/site[#ofmydomain.com]/web

Best regards

[Nology]

mlegler, sorry, bit confused by that response. I have seen other threads here that have had success with it, however they have been on RaQ 3 & 4's.

Any suggestions on how to get it working on a RaQ 550?

[mfalcon]

Has anyone come up with a solution to get the Aliasmatch working on a RaQ550? This is an extremely useful feature!

Thanks,
/\/\att

[BruceT]

You need to look at where the actual site web directories are located on the 550.

There are symlinks at /home/sites/www.example.com to /home/.sites/nnn/siteyyy but I'm guessing that Apache doesn't like the fact that they are symlinks which point to /home/.sites/nnn/siteyyy (where nnn and yyy are "random" numbers). The /home/sites links are only there to ease transition from the RaQ 3/4 way of dealing with sites to the RaQ 550 way.

[mfalcon]

BruceT
Yes, I've seen the directory structure and noticed the random site numbers. I guess it's a protection not allowing Apache access to the filesystem directly. What about a interim perl/php script that translates the domainname -> site# for Apache to 'read'? Any takers on this - is it possible? Maybe via a password protected script?

Thanks -
/\/\att

[BruceT]

Actually, Apache can access the files directly. That's how it serves the actual content.

What I was referring to was the symlinks themselves. There are options you can put into httpd.conf or .htaccess files to permit Apache to follow symlinks; it's generally not recommended though, as a bad guy could set up a symlink to something secret like /etc/passwd and Apache would blindly follow it.

I'm guessing you're trying to make domains visible that don't have DNS propogation completed yet...?

There should be a way to do it, especially as you can add Perl into the httpd.conf file if needed (although it can get a bit ugly if you're not careful) to look up the corresponding "real" path to the site indicated by the symlink... I don't have enough time in my schedule to tackle it myself directly though; sorry.