HTTPS Redirect not working after upgrade to Exchange 2007 SP2
I have weird situation happing this morning after upgrading my CAS and Mailbox server to SP2. I have followed the steps in TechNet article http://technet.microsoft.com/en-us/library/aa998359.aspxbut, it still does not work.When I configure everything as described in the article and try to access http://mail or http://mail.company.com I get the following error. "The website declined to show this webpage HTTP 403 Most likely causes:This website requires you to log in. What you can try: Go back to the previous page. More information This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage. For more information about HTTP errors, see Help."The weird thing is if I go under Tools>Options>Advance>Browsing and remove the check box next to "Show friendly HTTP error messages" it works. I have tested this on IE 8 and IE7 with no luck but, if I use Firefox it works. I am at a little bit of a loss as to what changed after the service pack.-ScottScott McNamee
October 22nd, 2009 7:29pm
Got it working. Did some searching and came across a post that says IE requires that the html code of the redirection page be at least 513 characters. So I added some padding to the code and it worked. Crazy.-ScottScott McNamee
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2009 11:14pm
Scott, Hi. I too have upgraded my environment to Exchange 2007, sp2. My redirect is now broken too. Previously, we had inserted "owaredirect.htm" and this was supposed to take http requests for our OWA farm to https://owa.xxxx.com/exchange but it no longer works. I just read your comments above. Can you tell me how you "padded" the htm page? Was this just a matter of adding additional characters? Help! Thanks, Eddie
July 18th, 2010 9:25pm
Here is what I have in my sslredirect.htm <html> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <head> <title>Microsoft Exchange - Outlook Web Access</title> <META HTTP-EQUIV="Refresh" CONTENT="0; URL=https://xxx.xxx.xxx/exchange"> </head> <body style="background-color:#000066;"> </body> </html>Scott McNamee
Free Windows Admin Tool Kit Click here and download it now
July 18th, 2010 11:54pm
Hi Scott. Thanks for the quick reply! I followed your lead on this, made modifications to ensure that I had at least 513 chars, but unfortunately, no dice. I still get presented with a forbidden access screen. My "owaredirect.htm" file looks like this: <html> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <!--This is a comment i need it to be greater than 513 characters --> <head> <!--<META http-equiv="refresh" content="0;URL=https://xxxxx/Exchange">--> <META http-equiv="refresh" content="0;URL=https://owa.xxx.xxxx.com/Exchange"> </head> </html> If you have any other suggestions, I'd appreciate it. (Especially since I've been on hold with Microsoft for 3 hours and no one has assisted yet.) Thanks!
July 19th, 2010 4:26am
Actually, the fix for this was quite simple: Thanks to an IIS specialist at MS, we simply changed the default web site so that it did NOT REQUIRE SSL. Once we did that, requests for http://owa were successfully re-directed to https://owa.xxx.xxxx.com/exchange. Thanks! Eddie
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2010 6:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics