When a browser connects to my website by entering it's FQDN the connection is encrypted using the site's SSL Certificate.
However it has come to my attention that it is possible to bypass the SSL and initiate an unencrypted connection by entering the load balancer IP Address (in which case you get an error saying it could not be encrypted).
The link below suggests that I could solve this with a redirect.
Apache reverse proxy so that SSL browser requests for IP of server are redirected to FQDN
Is this good practice or should I really be tying the certificate to the IP address in addition to the FQDN?
0 Answers