asked on
Exchange SP1 has broken my simple redirecting ASP file for OWA. Why? How can I fix it?
I did some reading around at one point because I wanted my users to be able to just go to any browser and type in 'mail.domain.com' and pull up the full/correct address for outlook web access.
I then read how to create a redirect by doing the following:
__________________________
In C:\INetpub\wwwroot of my Exchange 2007 server, I have a file called default.asp
The only text in the file is:
<% Response.Redirect "https://mail.domain.com/owa" %>
__________________________
This worked right away and worked great.
Only problem is last week I upgraded our Exchange 2007 server to SP1, and now it no longer works. I have absolutely no idea why.
Anyone have any ideas?
I then read how to create a redirect by doing the following:
__________________________
In C:\INetpub\wwwroot of my Exchange 2007 server, I have a file called default.asp
The only text in the file is:
<% Response.Redirect "https://mail.domain.com/owa" %>
__________________________
This worked right away and worked great.
Only problem is last week I upgraded our Exchange 2007 server to SP1, and now it no longer works. I have absolutely no idea why.
Anyone have any ideas?
Exchange
Last Comment
LeeDerbyshire
ASKER
I have not installed any updates since SP1... I wanted to sort through any existing issues first before I complicated the matter. Is this a known issue that a post-SP1 update would fix?
Thanks!
Thanks!
What happens now, instead of the redirect? Exchange SP1 should not affect this type of thing, since it is something you created outside of the Exchange environment.
ASKER
It's as if the file doesn't exist... I type in mail.domain.com and get taken to http://mail.domain.com and get a message about how the page can only be viewed over https
If I add the s then I'm good but I don't want my OWA users to have to do that.
If I add the s then I'm good but I don't want my OWA users to have to do that.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
OK Lee...
SSL has always been required for my OWA and Activesync users... but you're saying that the fact that SP1 has changed the default website to require SSL that my ASP file no longer works?
I went in and removed SSL required from the default website but it then complained that the policy didn't match activesync, exchange, and OWA. I said 'OK' without selecting any of the items on the list but it looks to me like it still removed the SSL requirement from them all. So I went back in and added them manually.
Looks like it's back to forcing SSL yet my redirect script is working again.
Thanks!
SSL has always been required for my OWA and Activesync users... but you're saying that the fact that SP1 has changed the default website to require SSL that my ASP file no longer works?
I went in and removed SSL required from the default website but it then complained that the policy didn't match activesync, exchange, and OWA. I said 'OK' without selecting any of the items on the list but it looks to me like it still removed the SSL requirement from them all. So I went back in and added them manually.
Looks like it's back to forcing SSL yet my redirect script is working again.
Thanks!
Getting the combination of requiring SSL, and using a redirect, can be tricky, and there are several documents that describe how to correctly implement this combination (they usually get rather complicated). But yes, if you require SSL on your Default Web Site, then any redirect will not work if you don't use https in your URL.
let me know
thanks.