| « Powershell to the rescue! | ssh/sftp for Windows 2008 Server using CopSSH » |
IIS7 adds the ability to use a 302 redirect response as a "Customer Error Page" instead of actually making a file with a html refresh or asp response.redirect. This is much easier to manage when you are doing redirects on several websites.
1. Select the website your are working with in IIS7, and make sure you are in the Feature View.

2. Double click "SSL Settings" and check Require SSL and click Apply.
3. Go back into the Feature View and open "Error Pages"
4. Click on Add and configure the following:
Status code: 403.4
Click on Respond with a 302 redirect and provide the https redirect URL.
*** NOTE HERE *** I had problems with redirection with some clients. I believe https://mysite.thisdomain.com and https://mysite.thisdomain.com/index.asp have different results in some web browser configurations. Changing all my redirection URLs to https://mysite.thisdomain.com/index.asp seemed to correct my problems.
Obvious, once you realize your mistake... :(