Re: [lvs-users] Random "Page cannot be displayed" with IE and SSL throug

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] Random "Page cannot be displayed" with IE and SSL through LVS loadbalancing
From: "Daniel Kerrutt" <d.kerrutt@xxxxxxxxxxxxxx>
Date: Thu, 26 Jun 2008 14:30:37 +0200
On Thu, Jun 26, 2008, Daniel Kerrutt wrote:
> On Wed, Jun 25, 2008, Joseph Mack NA3T wrote:
>> On Wed, 25 Jun 2008, Daniel Kerrutt wrote:
>>> Hi -
>>> I posted this subject to microsoft.public.internetexplorer.general,
>>> but wanted to ask for help here, too.
>>> I have a problem while connecting to a loadbalanced website via SSL.
>>> Sometimes IE is displaying an "Page cannot be displayed" error
>>> message. Sometimes the error is happening instantly, sometimes after
>>> entering the URL 3-4 times.
>>> Server software is Apache 2.2 / mod_ssl
>>> Keep-Alive is forced to turn off with the following configuration
>>> statement with SSL connections:
>>> SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
>>> downgrade-1.0 force-response-1.0
>> Graeme replied to a similar problem on 22 May (IE and
>> apache/ssl). Go look in the archives.
> The problem described there sounds very similar.
>> the source of the problem is described here.
>> I don't know why this is a problem through a director, but
>> not connecting directly, so I may not understand the problem
> Thanks for the link.
> The problem is definitly only while connecting through LVS.
> One problem described in the modssl FAQ is about the SSL session cache.
> Maybe there is a bug in IE because every request is directed to a
> different realserver, but IE is relying on SSL session cache reuse
> like described in the FAQ.
> I don't know the details how SSL session cache is working - but provided
> that the connection is working fine when connecting directly,
> this might be the source.
> Cheers,
> Daniel

Ok, finally its fixed..
Turned out that SSL session cache was not activated across all
realservers - so I did hit the IE bug.... *use head with wall*

<Prev in Thread] Current Thread [Next in Thread>