El Miércoles, 21 de Enero de 2009 01:42:45 Brian Mearns escribió:
> Is that right? I thought it was the opposite: most browser's supported
> SNI, but Apache doesn't. Is SNI done automatically when Named Vhosts
> are used, or are there additional directives required?
>
Well, actually most browsers
El Martes, 20 de Enero de 2009 22:49:36 John Oliver escribió:
> > I'm not familiar with the RHEL init scripts. However, looking at yours it
> > seems to me that you need to change more things if you want to get those
> > two instances work independently. For instance, you should also change your
El Martes, 20 de Enero de 2009 21:21:37 Brian Mearns escribió:
> On Tue, Jan 20, 2009 at 3:17 PM, John Oliver wrote:
> > If it would turn out to be easier to do this another way, that's fine.
> > But I remember it as always having been a no-no to even try to get SSL
> > working with VirtualHosts.
El Martes, 20 de Enero de 2009 20:40:29 John Oliver escribió:
> I have a server I need to rebuilt, and I want to move the SSL website on
> it onto another server (that already has it's own SSL website). I'm
> going to use eth1 on the second server with the MAC and IP of the first
> server, and make
El Martes, 30 de Diciembre de 2008 17:53:42 krist.vanbes...@gmail.com escribió:
> On 12/30/08, Miguel Angel Tormo Alfaro wrote:
>
> > I thought it could be a browser issue, however the same config in apache 2.0
> > doesn't behave this way. On the other hand I'm a
Hi all,
I recently installed an apache web server using version 2.2.9, and I'm having
strange issues with the SSL behaviour. I don't need client certificate
validation so I didn't use the directive SSLVerifyClient. However, as apache
asked for a client certificate, I changed the SSLVerifyClient
