Quote:
Originally Posted by slava
This is not good. Port 443 must be with SSL (HTTPS) and when you connect over telnet to Apache SSL port you don't see http-data.
https://dnsmanager/manager/dnsmgr must be work in web-browser, but you work without SSL over HTTP (not HTTPS) and for this reason does not work
|
Incorrect. We are only using HTTPS as we noted. A test for HTTPS over port 443 can be simply performed just as we outlined. I assumed you would recognize a valid response, so I didn't paste the normal extra response information, but since you think something is wrong on our end, I'll be happy to show you below:
---
telnet X.X.X.X 443
Trying X.X.X.X...
Connected to X.X.X.X.
Escape character is '^]'.
HEAD / HTTP/1.1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href="https://ourmaskedhost.com/"><b>https://ourmaskedhost.com/</b></a></blockquote></p>
<hr>
<address>Apache/2.2.3 (Red Hat) Server at ourmaskedhost.com Port 443</address>
</body></html>
Connection closed by foreign host.
---
As you should clearly see, SSL on port 443 is active. If it wasn't, we would have received an error as follows: "Could not open a connection to host on port 443 : Connect failed". Please learn about this topic before making incorrect statements.
And as we also clearly stated, we are *only* using SSL via the web browser, i.e., http
s://ourmaskedhost.com/manager/dnsmgr.
The problem has nothing to do with SSL.