IIS 403;4 custom error

I'm running IIS 5.0 and am having problems getting a customized error to work properly. I have a site that has a certificate on a secure directory. The default page for the site simply performs a redirect of the user to the logon page for the site, e.g., response.redirect ("https:\\www.mysite.com\secure\logonpage.asp"). I've configured the 403;4 custom error with a non-secure page that takes the user to an error messaging page which is also non-secure. If I turn off SSL within my browser and try to access https:\\www.mysite.com I receive "The page cannot be displayed" with the "Cannot find server or DNS Error" error. If I try to access the logon page directly with http:\\www.mysite.com\secure\logonpage.asp the site properly directs me to the error page. What am I missing?

Google turned up this, perhaps it will help

http://www.issociate.de/board/post/152620/SSL_Redirect.html

Doug: The thread you directed me to handles customizing an error to translate http to https. My problem is if I have SSL turned off on my browser accessing the web site doesn't seem to hit the customized error page. It goes directly to the DNS error.

I don't know, sorry.

Just a thought... what is generating the error? IIS or Internet Explorer (assuming thats what you're using)?

Also (I'll check this when I start doing some dev work again in mid jan) Can't you set custom errors for a specific directory in IIS, perhaps you have defined global ones, but the directory you're attempting to browse isn't configured correctly?

I configured the 403;4 at the Default Web Site level so it covers it all the way to the directory with security. As for what is generating the, I'm not clear as to where the DNS error comes from.

Maybe you can look in your IIS logfile and see what the requested url seen by IIS was (that didn't work). I haven't done much with SSL, sorry I'm not much help on this one.

Opened an incident ticket with Microsoft and they inform me that this custom error isn't used for this purpose. The 4.03;4 is to inform users that they are trying to hit a page using http when the protocol required is https. Microsoft also stated that what I want to do is controlled within the browser and allowing developers to capture this information would open up security holes in IE.