On Thu, Jan 8, 2009 at 1:28 AM, Krist van Besien
krist.vanbes...@gmail.com wrote:
On Wed, Jan 7, 2009 at 4:27 PM, Brian Mearns mearn...@gmail.com wrote:
Right, which I guess is a big problem for most use cases. For me, my
certificate is self-signed anyway, and I already use it for multiple
On Thu, Jan 8, 2009 at 8:03 AM, Bruno - e-comBR br...@e-combr.com.br wrote:
I think a bank site or a big e-business site won't HAVE TO use
virtual servers using another domains.
And I also think a common site don't need SSL.
I use SSL/TLS for privacy on my site, not for authentication per se,
This issue is similar to the issue of proxying HTTPS.
The only better option I see for web servers is to use only one
certificate for all the server, and the user will need to trust in the
server and ignore the wrong domain.
I think a bank site or a big e-business site won't HAVE TO use
virtual
2009/1/8 Brian Mearns mearn...@gmail.com:
On Thu, Jan 8, 2009 at 8:03 AM, Bruno - e-comBR br...@e-combr.com.br wrote:
I think a bank site or a big e-business site won't HAVE TO use
virtual servers using another domains.
And I also think a common site don't need SSL.
I use SSL/TLS for
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
On Thu, Jan 8, 2009 at 1:28 AM, Krist van Besien
krist.vanbes...@gmail.com wrote:
On Wed, Jan 7, 2009 at 4:27 PM, Brian Mearns mearn...@gmail.com wrote:
Right, which I guess is a big problem for most use cases. For me, my
On Thu, Jan 8, 2009 at 9:23 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
Is that possible if I want to serve both secure and unsecure (80 and
443)? If I just setup my root configuration (i.e., not in a vhost) to
listen on port
On Thu, Jan 8, 2009 at 9:29 AM, Brian Mearns mearn...@gmail.com wrote:
On Thu, Jan 8, 2009 at 9:23 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
Is that possible if I want to serve both secure and unsecure (80 and
443)? If I
2009/1/8 Brian Mearns mearn...@gmail.com
On Thu, Jan 8, 2009 at 9:23 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
Is that possible if I want to serve both secure and unsecure (80 and
443)? If I just setup my root
Bruno - e-comBR wrote:
2009/1/8 Brian Mearns mearn...@gmail.com
On Thu, Jan 8, 2009 at 9:23 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
Is that possible if I want to serve both secure and unsecure (80 and
On Thu, Jan 8, 2009 at 10:06 AM, Frank Gingras
francois.ging...@gmail.com wrote:
In a scenario where you have two vhosts on *:443, apache will serve the
certificate from the first vhost for both sites, therefore generating a SSL
certificate mismatch if a client were to request content from the
Brian Mearns wrote:
On Thu, Jan 8, 2009 at 10:06 AM, Frank Gingras
francois.ging...@gmail.com wrote:
In a scenario where you have two vhosts on *:443, apache will serve the
certificate from the first vhost for both sites, therefore generating a SSL
certificate mismatch if a client were to
On Thu, Jan 8, 2009 at 9:56 AM, Bruno - e-comBR br...@e-combr.com.br wrote:
2009/1/8 Brian Mearns mearn...@gmail.com
On Thu, Jan 8, 2009 at 9:23 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns mearn...@gmail.com wrote:
Is that possible if I want to
I know everyone always asks about having name-based-virtual hosts with
a secure connection, and I understand why it's not currently possible.
So I was thinking of ways around this, and I came up with a little
something. I haven't tested it yet, but I'm curious what people think.
The idea is to
On Wed, Jan 7, 2009 at 4:06 PM, Brian Mearns bmea...@ieee.org wrote:
The only obvious drawbacks I can think of is possible lag introduced
by having to proxy, and that all the sites would have to use the same
certificate (as defined in the port 443 vhost on the frontend
server).
And that is
Brian Mearns wrote:
for secure http support. The frontend server can then use rewrite
conditions to check the http Host header, and rewrite rules with the
And how can he check the host header if the request is encrypted? He has
to decrypt it. And to do so, he needs a certificate.
Davide
--
On Wed, Jan 7, 2009 at 10:13 AM, Davide Bianchi dav...@onlyforfun.net wrote:
Brian Mearns wrote:
for secure http support. The frontend server can then use rewrite
conditions to check the http Host header, and rewrite rules with the
And how can he check the host header if the request is
On Wed, Jan 7, 2009 at 4:27 PM, Brian Mearns mearn...@gmail.com wrote:
Right, which I guess is a big problem for most use cases. For me, my
certificate is self-signed anyway, and I already use it for multiple
hostnames (myserver.net, www.myserver.net, web.myserver.net, which are
all aliased
17 matches
Mail list logo
