> Here is another reason, if you intend getting positiones on a search engine
> , IP's are also needed, even with the normal Apache, reason...because the
> search engine crawlers can tell its a virt host and will not rate it
> highly, or at all possibly. I have taken the word of some people in the
*** REPLY SEPARATOR ***
On 16/06/00 at 8:14 Charles Galpin wrote:
>perhaps if I explain my experience with this, it will help
>
>On Thu, 15 Jun 2000, Brian Ashe wrote:
>>
>> 4) I cannot confirm or deny the single IP address theory, as I have not
>> tried it. But I do have som
perhaps if I explain my experience with this, it will help
On Thu, 15 Jun 2000, Brian Ashe wrote:
>
> 4) I cannot confirm or deny the single IP address theory, as I have not
> tried it. But I do have some trouble believing it since the ServerName
> directive is what gets matched against the cert
Brian:
Ti took the work done by Greg Wright and some others on the
apache-ssl-1.3.9.src.rpm and went in to make the customizations so it
would build a the apache-ssl-1.3.12.i386.rpm. So far, it seems to work
correctly. It even installs the apache-ssl stuff in it's own directory,
httpsd instead
Hi Michael,
1) Each domain must have its own certificate.
2) Each domain that does not use SSL must be specified as such. (Turn SSL
off for that domain)
3) Any domain that will provide both regular and SSL connections must have a
virtual host set up for each listening on the appropriate port.
"Michael J. McGillick" wrote:
> Is there a way to use one certificate (I'm using a fake one right now,
> until I get this set up) for each virtual domain I want to set up, or does
> each domain need it's own certificate? In either event, has anyone ever
> done this, or know the steps to set this
*** REPLY SEPARATOR ***
On 15/06/00 at 10:01 Brian Wright wrote:
>Hi, Mike!
>
>Each domain needs it's own certificate, I believe. :( They base it on the
>domain name, not the IP address. Thawte.com is a good place to go get
info
>on that.
>
Thats true, but what Charles poin
Hi, Mike!
Each domain needs it's own certificate, I believe. :( They base it on the
domain name, not the IP address. Thawte.com is a good place to go get info
on that.
BTW, where did you get the Apache-SSL? Did you use an RPM?
Thanks,
Brian
-Original Message-
From: Michael J. McGill
Mike
You cannot do this with name based virtual hosting. You need a seperate IP
for each domain you want to have a certificate for.
sorry,
charles
On Thu, 15 Jun 2000, Michael J. McGillick wrote:
> Good Morning:
>
> I'm running Apache-SSL 1.3.12 on my machine at home. I'm interested in
> set
