Hi, I thought there was a 'require SSL' option somewhere in IIS, but I can't find it now so maybe I was thinking of Apache or some other server...
Anyway, without that option my next choice would be IIS's wildcard redirection: http://support.microsoft.com/kb/324000 You set up a web site on port 80, and put wildcard redirection in it to redirect all requests for /Some/Page.html to https://myserver/Some/Page.html(the wildcard takes care of the page names and you can put them in the new URL). You then have your real site set up to only respond to SSL requests. That sounds like it would do what you want, but the wildcard redirection in IIS is powerful but under-documented. I think it should do what you need, but it might take a while to figure out the syntax. Good luck, Geoff On Mon, May 19, 2008 at 9:23 PM, Adam Tuliper <[EMAIL PROTECTED]> wrote: > You are saying if a user goes to one area that is http they must go to > https > - thats a redirect. the browser won't know it yet since the protocol is > http, not https, so as far as I know, you need at least a redirect to tell > the browser to handle ssl. > if you did a server.transfer. you are internally going to a new page, not > changing protocol, so you still must do some sort of redirect to have the > browser setup the ssl session. > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
