
Main Menu
Brad's TechTips - Exchange Server & Outlook
[<<
Full list of Exchange Server & Outlook tips.]
Outlook Web Access 2003: Redirect OWA From HTTP to HTTPS
When configuring OWA on Exchange 2003, you may want your users to access the site using HTTPS (SSL). However, if they type the URL using HTTP instead, they will receive a 403-4 error message in their browser rather than being redirected automatically to HTTPS. The following steps will setup an automatic redirect.
Outlook Web Access 2003: Redirect OWA From HTTP to HTTPS
When configuring OWA on Exchange 2003, you may want your users to access the site using HTTPS (SSL). However, if they type the URL using HTTP instead, they will receive a 403-4 error message in their browser rather than being redirected automatically to HTTPS. The following steps will setup an automatic redirect.
- Create a folder under Inetpub\wwwroot called "errors."
- Create a text-formatted file called httpsredir.asp in
the errors directory. Put the following lines into that file. (Note
that the code beginning with Response.Redirect
and ending with "/exchange" actually belongs on
a single line, even though it may not appear that way due to the browser
wrapping the text on this page.)
<%
If Request.ServerVariables("SERVER_PORT")=80 Then
Response.Redirect "https://" & Request.ServerVariable
("SERVER_NAME") & "/exchange"
End If
%>
- Open the Internet Information Services MMC and expand the Default Website. Select the
Exchange virtual directory, right-click and choose Properties. Go to the Custom Errors tab.
- Scroll down the list until you find 403-4, select it and click Edit. Select
URL as the Message Type from the drop down list and then enter
/errors/httpsredir.asp in the URL field. Click OK until you back at the default IIS console.
- Expand Default Website and select the errors directory you created earlier. Open the Properties page for the errors folder. Under the Directory tab and in the Application Settings area, click
Create. Select the ExchangeApplicationPool from the drop down lists next to Application Pool.
- Restart IIS by typing IISRESET at a command prompt.
- Done.
This information was collected from The Lazy Admin. Full credit goes to that site.