I've been using IIS6 for my web app installs and I force SSL by selecting force ssl in the certificate edit. However if a user types the url http:// rather than https:// the user gets a 403.5 error. I circumvent this by using a custom error page the redirects to the desired page using I thought I read somewhere that IIS7 resolves this, but as I look, I see similar solutions with the new addition(to me) of a custom httpmodule that basically does the same thing.
Questions: 1. Does IIS7 have a resolution for this? 2. What do you guys think about letting port 80 through anyways if the site is to be secured(I know users will type expecting to go to a secure site)?
Questions: 1. Does IIS7 have a resolution for this? 2. What do you guys think about letting port 80 through anyways if the site is to be secured(I know users will type expecting to go to a secure site)?
