Steve, Here's what you need to do...
2 Virtual Servers... 1. Secure server, with advanced settings allowing only secure access. 2. Unsecure server, with advanced settings allowing only unsecure access, and instead of getting content from a directory (like the above server), check the "redirection to a url" radio button to make the server redirect all requests to https://blah.blah.blah. If you need more help, email me off the list, and I'll send you a screenshot of the iis setup for this. --------- Now, for what we do here at my company... Before we built our content management system, and we used to build sites by simply creating a bunch of taf files, we would have a method in a tcf, or a branch to another taf, that checked the server settings, to see if it was secure or not, and if it was not secure, it would do an http redirect to the secure version of the exact same page, by building up a url from https://<@CGIPARAM SERVER>/<@APPFILEPATH>/<@APPFILENAME>?<@ALLTHEARGS> I've kinda paraphrased these tags, as I don't have time to get into the nitty gritty details... Then, we had another method, or branchable taf file that did the opposite, (if secure, redirect to unsecure) We would put a call to the "JumpToSecure" method on all pages that we wanted ssl used. We would also put a call to the "JumpToInsecure" method on some of the key pages that we didn't want ssl on, like the homepage, main navigation pages. This way, if someone started the checkout process, they would, "JumpToSecure", but if they left the checkout process, they would "JumpToInsecure" We found that it wasn't necessary to explicitly put "JumpToInsecure" calls in every non secure taf, just some key ones to get them out of ssl. This way you dont have the overhead of SSL with something as simple as your companies history page, but as soon as you start the checkout process you're protected. Today with our content management system, it as simple as a checkbox when creating a page as to whether or not you want to force ssl. Everything above is built into the CMS delivery engine. /John ----- Original Message ----- From: "Web Dude" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Thursday, September 26, 2002 8:19 AM Subject: Re: Witango-Talk: IIS and SSL > Okay, I haven't really tested this yet. But if you add this > javascript tag in the body of the html on the default page, it should > load the secure page. > > <script> > document.location="https://www.myserver.com"; > </script> > > >Has anyone been able to find the trick to setting up both an SSL and a > >non-SSL server on the same IIS machine under Windows 2000 Server? > > > >All I want to do is to set up a redirect on the non-SSL side of > >http://www.myserver.com to redirect it to https://www.myserver.com. I don't > >have two nic cards so I can't set up two IP addresses. What little > >documentation I did find is that you can't have two host headers when one of > >the is SSL. > > > >I need to find a workable solution. > > > >Thanks, > > > >Steve Smith > > > >Skadt Information Solutions > >Office: (519) 624-4388 > >GTA: (416) 606-3885 > >Fax: (519) 624-3353 > >Cell: (416) 606-3885 > >Email: [EMAIL PROTECTED] > >Web: http://www.skadt.com > > > >________________________________________________________________________ > >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > -- > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
