I recently ran into a situation in which a web server I was running could no longer serve HTTPS traffic (due to some SSL cert issues). Since the server could not process this traffic I could not use Apache redirect rules to redirect to non-https. I then tried redirecting X.X.X.X:443 to X.X.X.X:80 at my firewall/NAT device but couldn't seem to get it to work.
I'm not asking how to do this since it is specific to my infrastructure and devices. But is it possible to do this at all? A colleague suggested it may not be possible since the client is requesting a secure connection, and it was failing because we were responding with an insecure connection. This would be different than responding with a 302 and forcing the client to make a new request for non-https using apache redirects.