Re: wrong e-mail !!!!!!!!!!!!!!!!!!!!!!!

[email protected] Mon, 14 Jul 2008 19:24:46 +0000
Newsgroups gmane.comp.apache.mod-ssl.user
Message-ID <071420081924.25854.487BA7FE000A4200000064FE22230647629B0A02D2089B9A019C04040A0DBFCFCD0E05079D0A@att.net>
THANK'S 
-------------- Original message from "Shahadat Hossain" <[email protected]>: -------------- 


you know what, You are a f***en idiot.
if you do not want to receive these emails, just get your name taken off from the list instead of b-shitting. 

send an email to [email protected] address (you can also find it at the bottom of this message) with subject as 'Remove me'.

ok?


On Mon, Jul 14, 2008 at 7:10 PM, <[email protected]> wrote:

stop stop  sending me 
this bs , i have no idea  who are you !!!!
stop !!!!!!!!!!!!!!!
-------------- Original message from Dave Paris <[email protected]>: -------------- 


> It seem like you might be confusing "shared infrastructure" with 
> "single ip". As others have said, you need a distinct address for each 
> SSL-enabled httpd or proxy, although they can reside on the same hardware. 
> 
> A good example of this is the typical configuration for larger server 
> farms. You find multiple High Availability load balancers in the DMZ for 
> both http and https using something like ha/keepalived for linux. These 
> proxy the incoming request back into private address space. The SSL 
> proxies terminate the SSL connection and broker the request on behalf of 
> the user and everything goes to the private address space in plain http. 
> This allows each of the _real_ webservers to achieve better 
> performance since the SSL overhead is not present. 
> 
> While you can use Apache as an SSL-terminating proxy, I find I get 
> better performance, lower memory utilization and easier configuration 
> using Pound ( http://www.apsis.ch/pound/ ). Using keepalived, I have 
> multiple public IP addresses floating between several hosts and pound 
> binds https to those addresses. 
> 
> Hope that adds a bit of additional clarity, 
> Dave 
> 
> Cuesta Gilles sent forth: 
> > So what about this ? 
> > "*MULTIPLE CN (SAN) SERVER CERTIFICATES* 
> > 
> > This type of certificate (also called /Subject Alternative Name/ (SAN) ) 
> > enables to secure not only one website but a large number of sites (a 
> > list of sites) hosted on a shared infrastructure (server with multiple 
> > names, reverse proxy). Ideal to secure multiple brands of a corporation. 
> > One certificate per hardware is required." 
> > 
> > http://www.tbs-certificats.com/index.html.en 
> > 
> ______________________________________________________________________ 
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org 
> User Support Mailing List [email protected] 
> Automated List Manager [email protected]