IIS Server - Custom Error Page Issue

Author

Custom Error Page Issue

Joshbish1979

2005-12-23, 5:55 pm

I am running Exchange 2003 on a Windows 2003 server.

Recently IIS will not redirect http requests to OWA to https. I have
configured IIS per Microsoft's recommendations for redirecting users from
http to https, I have tested the owahttps.asp redirect script and find that
it works if I type it in directly. As far as I have been able to determine
IIS will no longer use a URL as a custom error page if you have SSL enabled
for that virtual directory, in this case the Exchange virtual directory. I
have checked everything else. It seemed to start after I installed FTP
services. Any help would be greatly appreciated.

David Wang [Msft]

2005-12-24, 5:56 pm

Just checking that you have dotted all i's and crossed all t's:
- Is the 403.6 CustomError setting that is actually effective for that vdir
(i.e. either set at that vdir or inherited, unhindered, to that vdir) set to
a URL that goes to your CustomError
- Is the vdir set to "SSL-Only" and not "either HTTP or HTTPS is ok"
- Is the CustomError URL in a vdir that allows HTTP. Because if the
CustomError URL is also SSL-only, you are in catch-22.
- Is the CustomError URL also in the same Application Pool as Exchange.

If the settings all look correct, then I suspect you have some ISAPI Filter
running that is confusing things.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Joshbish1979" <Joshbish1979@discussions.microsoft.com> wrote in message
news:C883B346-9C85-4252-BFAA-E7DAD8177423@microsoft.com...
>I am running Exchange 2003 on a Windows 2003 server.
>
> Recently IIS will not redirect http requests to OWA to https. I have
> configured IIS per Microsoft's recommendations for redirecting users from
> http to https, I have tested the owahttps.asp redirect script and find
> that
> it works if I type it in directly. As far as I have been able to
> determine
> IIS will no longer use a URL as a custom error page if you have SSL
> enabled
> for that virtual directory, in this case the Exchange virtual directory.
> I
> have checked everything else. It seemed to start after I installed FTP
> services. Any help would be greatly appreciated.

Joshbish1979

2005-12-27, 6:06 pm

1. I don't believe that the 403.6 error needs to be set, however I do have
the 403.4 set to display a custom URL located on my IIS server. This is set
specifically for the Exchange VDir.

2. The VDir of Exchange is set to require SSL.

3. The Custom URL is not in an SSL only VDir. Just standard HTTP and
anonymous access.

4. The Custom Error is in the Same application pool with the Exchange VDir.

As a note, I do not know if I mentioned this, but I am running Windows
Sharepoint services on this server. Also, this problem only started
occurring after I installed FTP Services.

Thanks.

"David Wang [Msft]" wrote:

> Just checking that you have dotted all i's and crossed all t's:
> - Is the 403.6 CustomError setting that is actually effective for that vdir
> (i.e. either set at that vdir or inherited, unhindered, to that vdir) set to
> a URL that goes to your CustomError
> - Is the vdir set to "SSL-Only" and not "either HTTP or HTTPS is ok"
> - Is the CustomError URL in a vdir that allows HTTP. Because if the
> CustomError URL is also SSL-only, you are in catch-22.
> - Is the CustomError URL also in the same Application Pool as Exchange.
>
> If the settings all look correct, then I suspect you have some ISAPI Filter
> running that is confusing things.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> "Joshbish1979" <Joshbish1979@discussions.microsoft.com> wrote in message
> news:C883B346-9C85-4252-BFAA-E7DAD8177423@microsoft.com...
>
>
>