Traditionally if one was to secure a web server using TLS (or previously, SSL) – then one would configure your web server to use TCP port 443 to listen for TLS requests from clients (browsers). When a browser connects to the web server using the HTTPS protocol, the server would encrypt the communications and all would be well with the world. A problem occurs when you use name based Virtual Hosting on your web server.

Have you ever had your website hit on a topic that people find conflicting? When the site gets viewed by the masses, you need to be prepared. If you have access to modify your web server .htaccess file then go and have a read of the Coral CDN Overview For those interested in the techie bits, here is my .htaccess for news site flood protection, and to allow CDN to serve up all my site images – thus offloading from my puny connection the bandwidth burden for images.