The only thing I can see as strange with that configuration is that you
didn't get an error with http://localhost:443. The server should have
responded that you used the wrong protocol, since it would expect an SSL
connection to that that port. that is why you have the s after http (to
indicate a
Colin Chalmers wrote:
>
> http://localhost works
> https://localhost works
> but http://localhost:443 returns a page but does not use a secure
> connection
What do you mean by "works"? Do they all lead to the same page?
I think what is happening is the following:
http://localhost - defaults t
