I used a cert with *.commercestore.com. This worked for me. You then need
to make a virtualhost for both ports 443 and 80 for each domain. The setup
varies between ben_ssl and mod_ssl, and there may be a few other
variations. Check the docs that came with your "ssl" add-on.
Nick
At 11:26 AM
Doh! I didn't mean name based, brain fart there. Each host has its
own ip#. All https requests are sent from the 'main' server(the actual
ip# of the machine and its corresponding pages), but http works fine.
Sorry for the brain fart there. Any ideas? :)
Morgan
___
Steven J Sobol schrieb:
>
> On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
>
> > When a SSL connection is established, the server will only see the IP
> > address (or IP/Port address), therefore the https request is always
> > resolved to be for your "main" server.
>
> I have n
On Tue, 20 Jul 1999, Steven J Sobol wrote:
> On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
>
> > When a SSL connection is established, the server will only see the IP
> > address (or IP/Port address), therefore the https request is always
> > resolved to be for your "main" se
On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
> When a SSL connection is established, the server will only see the IP
> address (or IP/Port address), therefore the https request is always
> resolved to be for your "main" server.
I have no experience with named SSL virtual hos
morgan wrote:
>
> I set up some name based virtual hosts on a linux machine with apache.
> [..]
> The virtual host part
> works fine for all 3, however if I go to https://blah.company.com it
> serves up the document root pages for www.company.com instead!??!?!
IMHO you can't use name based virtu
When a SSL connection is established, the server will only see the IP
address (or IP/Port address), therefore the https request is always
resolved to be for your "main" server. You can either configure multiple IP
addresses or different IP address/Port combinations for multiple SSL sites
on th
