We have setup a custom error to redirect users when they try to access a
site without using https.  This work fine for any site that doesn't use
asp.net.  When you goto a site that uses asp.net you get the following
error:
The specified request cannot be executed from current Application Pool

It is acting like it hasn't hit the 403.4 error yet, so my custom script
hasen't redirected to https yet.

Thanks,
Jim Field
fieldj@roberts.edu

[ Post a follow-up to this message ]

Asp.Net is using its own set of error pages. Take a look at the
configuration file, it's in there...

Jerry

"Jim" <fieldj@roberts.edu> wrote in message
news:u4LkrczJEHA.2844@TK2MSFTNGP10.phx.gbl...
> We have setup a custom error to redirect users when they try to access a
> site without using https.  This work fine for any site that doesn't use
> asp.net.  When you goto a site that uses asp.net you get the following
> error:
> The specified request cannot be executed from current Application Pool
>
> It is acting like it hasn't hit the 403.4 error yet, so my custom script
> hasen't redirected to https yet.
>
> Thanks,
> Jim Field
> fieldj@roberts.edu
>
>

[ Post a follow-up to this message ]

a) In ASP.NET you need to edit the <customErrors> section of the web.config
file.
b) The actual error page needs to be served from the same Web Application
Pool that the error is being generated from.

Cheers
Ken

"Jim" <fieldj@roberts.edu> wrote in message
news:u4LkrczJEHA.2844@TK2MSFTNGP10.phx.gbl...
: We have setup a custom error to redirect users when they try to access a
: site without using https.  This work fine for any site that doesn't use
: asp.net.  When you goto a site that uses asp.net you get the following
: error:
: The specified request cannot be executed from current Application Pool
:
: It is acting like it hasn't hit the 403.4 error yet, so my custom script
: hasen't redirected to https yet.
:
: Thanks,
: Jim Field
: fieldj@roberts.edu
:
:

[ Post a follow-up to this message ]

Hello Jim,

This is a knwon issue, matching the following two points can resolve
it:

1) In Web.config, just leave customError disabled to allow IIS handle
the 403.4 error code.
<customErrors mode="Off" />

2) Yes, as the error message indicated, the ASP.net application's
AppPool must be the same one as which the redirection page located.
For example:

ASP.net app in /WebApplication1
redirect.asp in root directory /
403.4 is pointed to /redirect.asp
The site root(home) directory's AppPool is DefaultAppPool.

Set WebApplication1 to also use DefaultAppPool and the error will no
longer occur.
Another work around is place a copy of redirect.asp into
/WebApplication1 and map /WebApplication1's 403.4 to use this local
page.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

[ Post a follow-up to this message ]