On 3 Jun 2006, at 00:56, William Scott Jordan wrote:
personal website. For the most part, this just means that we need
to change the style sheet and use Company X's URL instead of our
own. Because we could be looking at potentially thousands of
clients wanting to do this and because 99.9% of the site would remain
That's what I do on my new site. (well, it's a bit more elaborate
than just a stylesheet, but it is Host header based) So yeah, that is
a good way of doing things.
And then the bigger question is, is there any way to tell AOLserver
which SSL cert to use, based on the host information?
I don't think any server available can do that, for reasons already
explained. I would register some generic domain name, get a domain
level ("wildcard") cert for it and when your sites do switch to
secure for final checkout, send them to https://
sitname.genericdomain.com.
If you are indeed talking about 1000s of sites, it may be worth it to
look into some hardware crypto box that is able to serve that many
different domains with a seperate cert each, without having to run
thousands of nsd processes. But you would still need one IP per site
to make it work.
Cheers,
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
