pteeter
asked on
Exchange 2007 IIS 7 - owa redirect
I realize this issue has been posted about ad nauseam.
I'm trying to accomplish redirects to https and the OWA virtual directory for 4 specific cases of 'mistyped' URLs. What can I say, my user community is detailed-URL-entry challenged?!
1. http + public host name -> https + public host name + /owa
2. https + public host name -> https + public host name + /owa
3. http + public host name + /owa -> https + public host name + /owa
4. http + internal host name -> https + public host name + /owa
Per the MS Technet doc, http://technet.microsoft.com/en-us/library/aa998359.aspx, I've configured an HTTP Redirect on the Default Web Site to 'https + public host name + /owa'. I've also disabled the SSL requirement on the Default Web Site.
Some testing has led me to disable all redirects on sub directories, both physical and virtual (with appcmd.exe), except the owa subdir. On the owa subdir, for now at least, I have the same redirect as the Default Web Site. I've also enabled the SSL requirement on the owa subdir.
Scenarios 1, 2, and 4 are accomplished. Redirects occur exactly as I hope they will.
Scenario 3 is another story. Due to the owa subdir SSL requirement, http + public host name + owa gets a 403 Forbidden Access Denied error page. Honestly, I'm fine with this - I don't want my users to have non-secure access. But I guarantee someone is going to complain and claim they are physically or mentally unable to add the 's', making http into https.
So given, what I've configured and what is working just fine. How best to make the scenario 3 redirect work properly?
I'm trying to accomplish redirects to https and the OWA virtual directory for 4 specific cases of 'mistyped' URLs. What can I say, my user community is detailed-URL-entry challenged?!
1. http + public host name -> https + public host name + /owa
2. https + public host name -> https + public host name + /owa
3. http + public host name + /owa -> https + public host name + /owa
4. http + internal host name -> https + public host name + /owa
Per the MS Technet doc, http://technet.microsoft.com/en-us/library/aa998359.aspx, I've configured an HTTP Redirect on the Default Web Site to 'https + public host name + /owa'. I've also disabled the SSL requirement on the Default Web Site.
Some testing has led me to disable all redirects on sub directories, both physical and virtual (with appcmd.exe), except the owa subdir. On the owa subdir, for now at least, I have the same redirect as the Default Web Site. I've also enabled the SSL requirement on the owa subdir.
Scenarios 1, 2, and 4 are accomplished. Redirects occur exactly as I hope they will.
Scenario 3 is another story. Due to the owa subdir SSL requirement, http + public host name + owa gets a 403 Forbidden Access Denied error page. Honestly, I'm fine with this - I don't want my users to have non-secure access. But I guarantee someone is going to complain and claim they are physically or mentally unable to add the 's', making http into https.
So given, what I've configured and what is working just fine. How best to make the scenario 3 redirect work properly?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Indeed, just copied and renamed the 403.htm file.
Working perfectly.
You win!
Working perfectly.
You win!
ASKER
Turns out I needed to remove the redirect placed on the owa subdir to get this all working.
Otherwise, browser/server gets stuck in fun looping redirect situation.
I believe all is well now.
Otherwise, browser/server gets stuck in fun looping redirect situation.
I believe all is well now.
ASKER
If one didn't want to force all 403 errors to this redirect, how might it be accomplished?
Can I define a custom error page just for this virtual site?