rrsnider
11-13-2001, 12:11 PM
I have been through many threads regarding shared SSL. I am not sure if there is a way to get around the warning about not being the owner of the certificate. Is this true ? I have set up a subdomain (secure.mydomain.com) with SSL active. Should I setup clients as users within that domain or do a symbolic link back to them. Will either eliminate the warning ? Help !!!
gabeosx
11-13-2001, 03:01 PM
The easiest way to do this would to create a symlink to the /home/sites (I think thats it... not home right now so I cant check) to the home directory of the secure subdomain. You can than give your clients
https://secure.yourdomain.com/www.clientsite.com/
How do you create a symlink?
cyansmoker
11-13-2001, 06:01 PM
Originally posted by hoot
How do you create a symlink?
ln -s /home/yoursecurepath /home/userpath/securewww
rrsnider
11-13-2001, 10:21 PM
I am trying to do symlink from:
secure.mysecuredomain.com to www.site8.com
I entered this command (from /home/sites/mysecuredomain.com/web directory):
ln -s /home/sites/site8/web site8
I then chown nobody site8
When I try to access https://secure.mysecuredomain.com/site8/index.html, I get the following error: The server encountered an internal error or misconfiguration and was unable to complete your request.
However, if I change my symlink statement to be:
ln -s /home/sites/mysecuredomain.com/web/index.html site8,
I can access https://secure.mysecuredomain.com/site8 and it brings up the index.html page.
Any idea what I am doing wrong here?
I wanted my customers to be able to access their sites before the dsn transfer was sone so I create a directory called sites in mydomain.com
then I typed in
ln -s /home/sites/www.mydomain.com/web/sites /home/sites it seems to have created a link but it doesn't work !
I have tried www.mydomain.com/sites/www.customerdomain.com/web and nothing comes up !
Any idea why it doesn't work?
Hoot