That does seem to be related. There appears to be some issue with older IEs
trying to establish an SSLv3 connection, so they need to be forced to SSLv2.
The problem was fixed with the following two settings in the nsopenssl section
of the config
ns_param protocol SSLv2
ns_param CipherSuite
This is from our FAQs:
Q: Whenever I want to pay in there is the massage "Page can not be found"?
A: Go to the menu bar of the internet-explorer (internet window) and press on
"Extra" - "Internetoptions". You will see some index cards. Please select the
card at the right hand, named "advanced". S
We had this problem with some of our customers on older IEs too. Everything
worked fine, except the https pages. We found out, that the HTTP 1.1
implementation of IE was faulty, so we told our customer to set their
preferences to HTTP 1.0. I don't know anymore if there was some additional
trick, bu
+-- On Feb 26, Elizabeth Thomas said:
> We are having problems here with an international site returning broken
> images from https requests from older IE browsers.
Define "international site". Do you have non-ASCII characters in your
URLs? Does your access log indicate that IE is asking f
Taking a shot that someone might recognize this:
We are having problems here with an international site returning broken
images from https requests from older IE browsers. With IE versions less
than 5.5 they are getting broken images. (The pages are fine on other
browsers). Previously they were al
