I currently have a site with multiple HTTP bindings and one HTTPS binding. The cert I'm using for it is specific to one domain (secure.domain.com) and IIS is responding to HTTPS requests over all bindings. I'd like to prevent that! Aside from users randomly navigating our site over HTTPS and ignoring the certificate error, bots have been indexing over HTTPS as well.
The simple solution was to add the binding to a new site and point that site at the same directory, however due to licensing issues I won't be able to do that with this instance.
I've tried giving the cert a friendly name with a * in the beginning and setting the host name, but it didn't seem to work.
Thanks for any ideas!