https:// pointing to the newest user's https directory

[sde]

i have a strage behavior:

domain1.com was setup a long time ago.

domain2.com is new.

https://domain1.com/ is reading the directory of /domain2/private_html/

both domains are on a shared IP, but should that matter?

 

[nobaloney]

One problem that comes to mind is that shared IP#s can't be used for https.

Jeff

 

[sde]

i have a ssl cert setup for the entire server, and i thought that if i didn't care about the 'domain mismatch' warning popup, it would at least point to the correct domain's private_html directory.

 

[nobaloney]

Nope.

If you don't have SSL turned on for the domain (and you can't, on a shared IP#), then the SSL section of the httpd.conf file isn't even created.

So by default apache looks at the first SSL section it can find for the IP#.

Which is the wrong one.

Jeff

 

[sde]

Thanks for helping me understand Jeff. I appreciate it. I thought I may have had something messed up on my server. It's much nicer to know it's working as expected

 

[nobaloney]

We had the same problem today troubleshooting a Cobalt RaQ 4 which had two domains sharing an IP# and one of them had a secure cert.

When the owner of the other domain typed in https by accident she thought the other party had "hijacked" or site.

Jeff