Question : Problem: Website SSL/TLS issue causing "Internet Explorer cannot display the webpage." to be displayed.

Problem: Website SSL/TLS issue causing "Internet Explorer cannot display the webpage." to be displayed.

Certificates were just updated causing users that run IE6 and higher versions that don't have TLS checked off under Advanced Settings to display "Internet Explorer cannot display the webpage."

Since this isn't a 404 error, by which I could normally change the error message, this message is being displayed by the user's browser.

My question is .. when the user doesn't have the option for TLS checked off inside of IE .. how can I deliver a custom message to the user.  

We are running Oracle's WEBLOGIC on our server, not IIS.

How can I do this?

Gary

Answer : Problem: Website SSL/TLS issue causing "Internet Explorer cannot display the webpage." to be displayed.

There is nothing you can do on the server to present a custom error page because the issue comes up during the connection negotiation between the browser and the weblogic web server.

http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/secmanage/ssl.html#1191073

make sure that the weblogic serverr component includes the following line:
-Dweblogic.security.SSL.protocolVersion=ALL

I am at a loss as to why you are trying to come up with a way to inform the user as to the cause of the issue rather than correcting the issue on your server.

The reason why they are having an issue.  lets try this Latin is the original language like SSL.
Italian is evolved from latin (TLS).

Your business caters to both Latin and Italian Speakers.
You have a schedule issue such that only Italian speaking individuasl showed up.
A Latin speaking individual comes in. The Latin speaker and the Italian speaker can not reach an agreement on a language to communicate. Provided no other common way to communicate exists, the Latin speaking person will simply walk away.

This is what happens between a browser that does not have the TLS 1.0 option enabled when it connects to your server that only supports TLS 1.0 communications.
The failure occurs during the exchange/negotiation of the connection such that there is no way the web server can convey to the user the reason for the issue via a connection that can not be established.