This has to be the least helpful reply on DO EVAR.

Well there was nothing else to say really :)

Why are you even trying to do this? It makes no sense to perform a HTTPS to HTTP redirection. It seems like you may not understand what HTTPS is about.

Thank you, I fully understand what https is about. We are not using ssl and don’t have a need for it. But we do need to cover our basis for the edge case someone accidentally verbosely enters https:// and have it do something more elegant than tell the user that this site isn’t secure. I just want it to silently redirect to the http:// version. I really don’t see what the issue is and why that is so odd.

The reason it’s odd is because the requirements for setting the redirect are the same as for just setting up SSL in the first place. So once you’re done, there’s literally no reason to do the redirect anymore, because users could just naturally use SSL when browsing your site instead.

If you don’t want users to be told the site isn’t secure, I suggest closing off port 443 (with a REJECT response rather than DROP) so that users aren’t mislead into believing the site is secure, and don’t have to see that annoying pop-up.

Otherwise, like I said - you can’t do this with your current requirements.