Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running on a Windows 2K3 server with IIS 6.

Due to some issues, I'd like to remove the SSL binding, and have traffic redirected to HTTP.

Where this becomes a problem, when a client tries to connect over https, there's nothing on port 443, so it gets a Cannot_Connect error instead of a 404. My thought is that this occurs before IIS. Is there a way to catch and redirect this error w/o having to leave the binding and just doing a simple IIS redirect? I'm removing the cert to resolve a security problem (needs to be done quickly due to the server being migrated and the security team wants a remediation to a vulnerability with the cert) so I don't want to keep the cert around.


share|improve this question
up vote 2 down vote accepted

Unfortunately you need to have something listening on port 443 to be able to have an HTTPS request redirected to HTTP. Also, the SSL handshake including the server sending its SSL certificate has to take place prior to the client being able to send in its HTTPS request.

When using HTTPS (SSL) everything is encrypted including the URL containing the HTTPS request.

share|improve this answer
That's what I was afraid of. Was hoping there was something in Windows that I could modify. – Dustin Aug 8 '12 at 16:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.