Can't possibly be a keep-alive problem with the following line is in the config:
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
I can however think of another issue with MSIE which may cause such behaviour.
Do you happen to apply compression? (mod_deflate)
In that case make sure that JS and CSS are NOT compressed when served to MSIE.
And as says Bowl, "a quick test would tell a lot..."
-ascs
-----Message d'origine-----
De : Boyle Owen [mailto:Owen.Boyle@xxxxxxx]
Envoyé : vendredi 1 février 2008 09:15
À : users@xxxxxxxxxxxxxxxx
Objet : RE: Customers getting "Page Cannot be Displayed" over SSL
> -----Original Message-----
> From: Douglas Hobaugh [mailto:doug@xxxxxxxxxx]
> Sent: Thursday, January 31, 2008 5:33 PM
> To: users@xxxxxxxxxxxxxxxx
> Subject: Customers getting "Page Cannot be Displayed"
> over SSL
>
> Hi all, I hope this is the correct list. First time posting.
>
> I am getting a lot of customers complaining that they get "Page Cannot
> be Displayed" errors when they connect to our SSL server.
Browser messages are practically worthless - what's in the error log?
Otherwise, guessing... hostname/common-name mismatch, cipher mismatch, keep-alive problems... you name it.
Is your site top-secret? Because a quick test would tell a lot...
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|