I just choose one good generic domain, ie: secure.mydomain.com, get that
signed, and put anything that's passing sensitive info(sign-ups, forms,
logins,etc) to that location. I've found it much better to send users
to another domain that has a signed cert. then to keep them in the
domain with an
I just choose one good generic domain, ie: secure.mydomain.com, get that
signed, and put anything that's passing sensitive info(sign-ups, forms,
logins,etc) to that location. I've found it much better to send users
to another domain that has a signed cert. then to keep them in the
domain with an
Greetings,
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on browsers, due to certificate not matching
most of the sites names. But
On Tue, 5 Nov 2002, DEFFONTAINES Vincent wrote:
Since I read several at several places on the Web that it was not possible
to build several HTTPS VirtualHosts on the same IP/Port, I'd like to add
this to the discussion.
Your comments will be appreciated.
IMHO if you want secure connection
On Tuesday, 2002-11-05 at 11:00:46 +0100, DEFFONTAINES Vincent wrote:
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on browsers, due to certificate not matching
most of the sites names. But it does work.
I disagree ;). It works in your eyes but the user will only see the
warning pop-up. That will
On Tue, Nov 05, 2002 at 11:00:46AM +0100, DEFFONTAINES Vincent wrote:
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on
Greetings,
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on browsers, due to certificate not matching
most of the sites names. But
On Tue, 5 Nov 2002, DEFFONTAINES Vincent wrote:
Since I read several at several places on the Web that it was not possible
to build several HTTPS VirtualHosts on the same IP/Port, I'd like to add
this to the discussion.
Your comments will be appreciated.
IMHO if you want secure connection
On Tuesday, 2002-11-05 at 11:00:46 +0100, DEFFONTAINES Vincent wrote:
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on browsers, due to certificate not matching
most of the sites names. But it does work.
I disagree ;). It works in your eyes but the user will only see the
warning pop-up. That will
On Tue, Nov 05, 2002 at 11:00:46AM +0100, DEFFONTAINES Vincent wrote:
I managed to create several Virtualhosts on a apache-ssl (1.3) server (same
IP, same port, several names).
The trick is to use the same Certificate for every Virtualhost, which will
of course generate a warning on
12 matches
Mail list logo
