https redirect

[wheel]

I'd asked about this question here:
[webmasterworld.com...]

Would like some further clarification.

Site A used to have an SSL cert, now discarded. Now when I visit [siteA.com...] it of course goes to the first site on my server (say site B) with an SSL cert - it shows content from site B. And I think this is causing me problems with ranking in Yahoo.

Do I have to set up https: again for site A to do the 301? Seems like that means I have to burn an IP. Can I not set up, inside the apache config for site B (the first SSL site in the server, so it's the one that gets shown by default) that says 'if you were actually looking for https on site A, then 301 over to the non-https version on port 80?

[Caterham]

Can I not set up, inside the apache config for site B

If you don't mind getting a certificate domain mismatch error/warning, yes.

[wheel]

Huh. what does that mismatch error do to the SE spiders?

if it's just a mismatch, and then the 301, or they ignore the error and do the 301, then that works fine for me.

[g1smd]

It is not what it does to spiders. It is the reaction of customers who are told that the security certificate is 'dodgy'.

[wheel]

It's not customers - there's few if any links going to https:. It's the SE's that I want to do a 301 for so that I don't have another domain showing content on my site.