|
(2008.05.22, 12:01)
Graeme:
You were right! I inserted this right after the "Listen 443" in the
Apache SSL configuration:
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
as opposed to the 'BrowserMatch ".*MSIE.*"' instruction that I already
had. And this worked! After about 50 page tests, no errors were
reported.
Thanks again. And let's all pray for the demise of Internet Explorer.
Benoît
> On Thu, 2008-05-22 at 10:19 -0400, Benoit Gauthier wrote:
>> Here are observations from our most recent tests. We can replicate the
>> problem fairly easily. The problem does NOT recur if we limit the
>> <img> tags on the page to a single image. If we add a second <img> tag
>> (coded as <img src=dir/image.gif>), we can produce the problem.
> Hrm. Has your Apache SSL config got the following lines?
> SetEnvIf User-Agent ".*MSIE.*" \
> nokeepalive ssl-unclean-shutdown \
> downgrade-1.0 force-response-1.0
> They can be set in the vhost context, or globally.
> Also, have you got keepalives switched on in your Apache config?
> This smacks to me of an app level problem being winkled out by the use
> of LVS, but I could be wrong.
> Graeme
|
