HTTP to HTTPS redirection for multiple URL's

Question for you guys that are the pro's:

I have 2 different URL's pointing to my exchanges OWA:

http://outlook.companyA.com and http://outlook.companyB.com

We want to force SSL and want to redirect both URL's to their HTTPS respective url.  I understand the process of a simple URL redirect through IIS however we want to preserve the URL's (ie. companyA and companyB) of the address so we don't ruffle feathers.  Thanks for any assistance you guys may be able to provide....
jriggyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ghoti_AZCommented:
Sounds like an HTTP 301/Redirect on each of the two URLs would be your best bet.  

301 Redirect Using IIS

In internet services manager, right click on the file or folder you wish to redirect.
Select the radio titled "a redirection to a URL".
Enter the page that the page will be redirected to.
Check "The exact url entered above" and the "A permanent redirection for this resource".
Click on 'Apply'.

In this case, you would redirect the folder corresponding with http://outlook.example.com to https://outlook.example.com.
0
jriggyAuthor Commented:
I was wondering whether a wilcard redirect would work, something like this:

http://outlook.*.com/Exchange/; https://outlook.$0.com/Exchange
0
Ghoti_AZCommented:
Are you expecting to have a cornucopia of other hosted sites that will need the redirect?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

jriggyAuthor Commented:
NO, just the two for the foreseeable future...
0
Ghoti_AZCommented:
In that case, setting up the two 301s would probably be wiser- you never know if some buffer overrun exploit using wildcards might come along.  In my opinion, it's better to not open any more doors than you have to.
0
jriggyAuthor Commented:
Found the answer myself:

To configure IIS to automatically redirect HTTP requests as HTTPS requests, follow these steps.

Important If the following conditions are true, you must mount and start the mailbox store before you can successfully complete these steps:

    * Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 is installed on a front-end server.
    * The mailbox store has been dismounted.

Note Follow these steps on an Exchange front-end server that communicates with a clustered Exchange back-end server.

   1. Create an Active Server Pages (ASP) Web page that contains the following code:

       <%

      If Request.ServerVariables("HTTPS")  = "off" Then
                                          Response.Redirect "https://" & Request.ServerVariables("HTTP_HOST") & "/Exchange"
      End If

            %>

   2. Name the Web page "Owahttps.asp".
   3. In Windows Explorer, create the Inetpub\Wwwroot\CustomErrors folder, and then save the Owahttps.asp Web page file to that folder.
   4. Start the IIS console.
          * In Windows NT Server 4.0 (IIS 4.0)

            Note Follow these steps if you are running Microsoft Exchange Server 5.5 Outlook Web Access on Windows NT 4.0 Server with the Windows NT 4.0 Option Pack. If you have an Exchange Server 5.5 mailbox server, and if the Outlook Web Access component is installed separately on a dedicated Web server, follow these steps on the Web server only.
               1. Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Services, and then click Internet Services Manager.
               2. Expand Internet Information Server, expand Computer Name, and then expand the Web site that the Outlook Web Access users use to access their Exchange server. By default, this Web site will be the default Web site.
               3. Go to step 5.
          * In Windows 2000 Server (IIS 5.0)

            Note Follow these steps if you are running Exchange Server 5.5, Exchange 2000, or Exchange 2003 Outlook Web Access on Windows 2000 Server.
               1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
               2. Double-click Computer Name to expand the computer object.
               3. Expand the Web site that the Outlook Web Access users use to access their Exchange server. By default, this Web site will be the default Web site.
               4. Go to step 5.
          * In Windows Server 2003 (IIS 6.0)

            Note Follow these steps if you are running Exchange 2003 Outlook Web Access on Windows Server 2003.
               1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
               2. Expand Computer Name, and then expand Web Sites.
               3. Expand the Web site that your Outlook Web Access users use to access their Exchange server. By default, this Web site will be the default Web site.
               4. Go to step 5.
   5. Right-click the CustomErrors folder, and then click Properties.
   6. Under the Application settings section, click Create.

      Make sure that CustomErrors is displayed in the Application name box.

      Note For Exchange 2003 running on IIS 6.0, click ExchangeApplicationPool in the Application Pool list.
   7. Click the Documents tab, and then add the Owahttps.asp file to the Enable default content page. Move the Owahttps.asp file to the top of the list.
   8. Click the Directory Security tab, and then click Edit under Authentication and access control.
   9. Click to select Enable anonymous access, and then click OK.
  10. Under Secure communications, click Edit.
  11. Click to clear the Require secure channel (SSL) check box, and then click OK two times.
  12. Right-click the Exchange virtual directory, and then click Properties.
  13. Click the Custom Errors tab, and then double-click 403.4.
  14. In the Message Type list, click URL.
  15. In the URL box, type /CustomErrors/Owahttps.asp, and then click OK.
  16. Click the Directory Security tab.
  17. Under Secure Communications, click Edit.
  18. Click to select the Require secure channel (SSL) check box.

      Note If you want to require 128-bit encryption, click to select the Require 128-bit encryption check box.
  19. Click OK two times.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jriggyAuthor Commented:
no objections?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.