Guys:
For many errors, Internet Explorer indiscriminately displays an internal error page that says “Page cannot be displayed” and then “Cannot find server or DNS Error” at the bottom.
IE displays this internal error page for:
- Server DNS entry not found
- Server DNS entry found but server is not listening on port
- Server and port are up, but HTTP connection attempt was made to HTTPS port
- Server and port are up, but HTTPS connection attempt was made to HTTP port
- The page required an X.509 client certificate for authentication, but an HTTPS connection attempt was made without a certificate or using a faulty certificate.
[ In case of a 404 error response, IE may display a shorter, different internal message: “The page cannot be found”, or the site’s custom page may be displayed]
Since Mozilla is a developer focused browser, it makes for a much better debugging tool. For example, in the case #5 above (X.509 certificate), Mozilla explicitly popped up a dialog saying:
“Could not establish an encrypted connection… certificate rejected… Error code:-12771”. IE, in contrast just showed its misleading “Cannot find server or DNS Error” error page (when in fact the server was up). Mozilla also lets you save the SSL response from the server in case #4 above.
Gerald was getting a certificate message from his server - if he uses Mozilla, he should be able to figure out what exactly is going on with his connection (handy, given that WM’s logging seems non-existent for HTTPS/ X.509 connections)
VR, you said:
> Make sure that in the certificate that you generated, the
> “Issued To” field has to match your URL domain ie. your ip
> address. Please make sure that this is correct.’
This is best practise, and most browsers (eg: IE) do carry out this check. I believe however, as far as WM is concerned, the “Is certificate CN = DNS entry?” check is not done for incoming connections authenticating with X.509 certificates. I am not sure about the WM check for outbound deliveries (i.e. Does WM check the remote server certificate = it’s DNS entry) – however, I would be surprised if it did. The reason for this laxity could be the performance hit reverse-resolving IP addresses to DNS entries, and that some organizations put machines on the Internet only specified by their IP address (i.e. they have only an IP address with no corresponding DNS entry). If Gerald is doing a browser based test Mozilla should just let him in with just a warning.
#webmethods-Protocol-and-Transport#webMethods#Integration-Server-and-ESB