According to what little documentation I've found on this subject, you cannot set up multiple host headers when SSL is involved. Or maybe it is that you cannot set up multiple sites using host headers when one of the sites is an SSL site.
I think that changing the error page (403-4.htm) has done what we needed, I'm just wondering if making a change to a file like this will cause problems down the road? Any ideas? 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 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Grieve > Sent: September 26, 2002 6:36 AM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: IIS and SSL > > > Steve, > > With IIS, you'd set up a site with the appropriate Host Headers and > effectively enable both HTTP and HTTPS access to that site. > > So, if I understand your problem, you want to 'trap' anyone > arriving at the > non-SSL URL and bump then to the secure version. However, both sites are > running the same virtual Web server, so how do you know..? Is that right? > > I think you need to look into the <@CGIPARAM SERVER_PORT> tag... which > should (I've never tried it) contain either "80" or "443", and use that to > determine whether your secure or not. > > Jon > > > > > -----Original Message----- > From: Steve Smith [mailto:[EMAIL PROTECTED]] > Sent: 26 September 2002 1:56 > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: IIS and SSL > > > I re-read my original post and I realized that I left out something in my > description. Nothing is is to be accessed from the non-SSL side of things. > This is for a subdomain (call it store.myserver.com). Everything > should pass > through the SSL side. Right now, if a user types in > http://store.myserver.com/ they would get an error page stating: > > ***** > The page must be viewed over a secure channel... try typing in > https... yada > yada yada > > HTTP 403.4 - Forbidden: SSL required > Internet Information Services > ***** > > What we want is to avoid having any user from every seeing this error > message. I thought that the solution would be to have a default > page set up > for http://store.myserver.com which would contain a redirect to > https://store.myserver.com/main.taf but I can't seem to be able to set up > http://store.myserver.com. > > I just solved my own problem although it might not be the best solution. I > simply added the redirect to the 403-4.htm file which I found in > winnt\help\iishelp\common. If anyone knows of a reason why I shouldn't > modify that file, please let me know. > > 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 > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Web Dude > > Sent: September 25, 2002 4:06 PM > > To: Multiple recipients of list witango-talk > > Subject: Re: Witango-Talk: IIS and SSL > > > > > > I am running SSL and non SSL on one server. I guess I don't > > understand your question. > > > > You do not need 2 nic cards for 2 IPs. Just go to the tcp protocol in > > networks and click on the advanced button and there you can add as > > many IPs as you need. > > > > As for the redirect. You still don't need 2 IPs for this. A site can > > be accessed via http or https as long as the Cert is installed > > correctly. In other words, if I go to http://www.myserver.com and > > view a page, it is from the same IP and domain name as if I was > > viewing https://www.myserver.com. The page is the same, it's just > > that one is secure and one is not. > > > > Note, however, if you do not pass the <@UserReferenceArgument> from > > http to https, you will lose all your variables. > > > > >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 > ________________________________________________________________________ > 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
