Google indexing example.com:443

[AjiNIMC]

link to http://example.com:443/ and it will index with following sentences

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: [example.com...]

Regards,
Aji

[edited by: tedster at 3:26 pm (utc) on Aug. 21, 2008]
[edit reason] switch to example.com [/edit]

[tedster]

Including a port number in a url is one of many potential canonicalization problems [webmasterworld.com]. In this case, it's a good guess that the server response sends the error message, but the status code in the http header is probably a 200 OK.

In other words, it's a custom error message that was not set up properly, and it leaves the wwebsite vulnerable to duplicate url issues. The fix, simply enough in this case, is to send the correct status code along with the custom error message.