-Original Message-
From: Justin Pasher [mailto:just...@newmediagateway.com]
Many others have provided some information, but here's a
basic summary
(assuming no SNI support):
(a) Single FQDN, single DocumentRoot - Single IP.
(b) Multiple FQDN, single DocumentRoot - Single IP,
* Boyle Owen owen.bo...@six-group.com [2009-12-15 10:22]:
-Original Message-
From: Justin Pasher [mailto:just...@newmediagateway.com]
(a) Single FQDN, single DocumentRoot - Single IP.
(b) Multiple FQDN, single DocumentRoot - Single IP, assuming cert
supports all (sub)domains
Peter Schober wrote:
* Boyle Owen owen.bo...@six-group.com [2009-12-15 10:22]:
-Original Message-
From: Justin Pasher [mailto:just...@newmediagateway.com]
(a) Single FQDN, single DocumentRoot - Single IP.
(b) Multiple FQDN, single DocumentRoot - Single IP, assuming cert
supports
Hi,
My company is wanting to keep this configuration for port 80 and add an
SSL certificate for just the www.example.com and example.com hostnames. Is
it possible to have Virtualhosts for just the 443 port and still allow
*.example.com to react the same way it does now?
Yes, it is. However,
Serge Fonville wrote:
Hi,
My company is wanting to keep this configuration for port 80 and add an
SSL certificate for just the www.example.com and example.com hostnames. Is
it possible to have Virtualhosts for just the 443 port and still allow
*.example.com to react the same way it does
Justin Pasher wrote:
Serge Fonville wrote:
Hi,
My company is wanting to keep this configuration for port 80 and
add an
SSL certificate for just the www.example.com and example.com
hostnames. Is
it possible to have Virtualhosts for just the 443 port and still allow
*.example.com to react
Dan Schaefer wrote:
So are you suggesting that I need multiple public IPs to implement
this, or just multiple private IPs? Private IPs is not a problem,
however, due to the fact that we have limited public IPS in our range,
it could be a problem when if and when we add new SSL certs. We would
Justin Pasher wrote:
Dan Schaefer wrote:
So are you suggesting that I need multiple public IPs to implement
this, or just multiple private IPs? Private IPs is not a problem,
however, due to the fact that we have limited public IPS in our
range, it could be a problem when if and when we add
Does it help to mention that my example.com and www.example.com certificates
are the exact same cert? My apologies for not mentioning this in the
beginning. If and when we do add SSL to other subdomains, they will be
different certs. I don't see that happening in the near future, however.
Roger wrote:
Does it help to mention that my example.com and www.example.com certificates
are the exact same cert? My apologies for not mentioning this in the
beginning. If and when we do add SSL to other subdomains, they will be
different certs. I don't see that happening in the near future,
* Roger rno...@gmail.com [2009-12-14 17:26]:
Is the content under example.com and www.example.com the same?
If it is, then just redirect all requests to example.com, www.example.com to
one
location. You don't need two certificates. In my opinion, if it is the same
content then having
Peter Schober wrote:
* Roger rno...@gmail.com [2009-12-14 17:26]:
Is the content under example.com and www.example.com the same?
If it is, then just redirect all requests to example.com, www.example.com to one
location. You don't need two certificates. In my opinion, if it is the same
If both vhosts are accessed via https you'll need both covered, as the
ssl connection happens before the redirect (as has been pointed out
dozens of times in recent weeks),
-peter
The situation that I was talking about is that if someone access
http://example.com or http://www.example.com
* Roger rno...@gmail.com [2009-12-14 17:47]:
The situation that I was talking about is that if someone access
http://example.com or http://www.example.com
then redirect to either https://www.example.com OR https://example.com.
Sure.
But of course, you cannot stop someone for trying to access
http://markmail.org/message/yr52ptnpgbocgvad
But we should just push for SNI, I guess.
-peter
Yea I agree.
-r
-
The official User-To-User support forum of the Apache HTTP Server Project.
See
Dan Schaefer wrote:
Does it help to mention that my example.com and www.example.com
certificates are the exact same cert? My apologies for not mentioning
this in the beginning. If and when we do add SSL to other subdomains,
they will be different certs. I *don't* see that happening in the near
Dan Schaefer wrote:
My company is wanting to keep this configuration for port 80 and add an
SSL certificate for just the www.example.com and example.com hostnames.
Is it possible to have Virtualhosts for just the 443 port and still
allow *.example.com to react the same way it does now?
17 matches
Mail list logo
