使用httpErrors(Redirect模式)遇403错误，生产环境404/500异常求助

Let’s walk through the likely causes of your production server issues and how to fix them—since your setup works locally/testing, the problem is almost certainly related to IIS configuration or permission differences in production.

First, Diagnose the Blank Page #

The blank page usually means either:

• Your custom error page isn’t being loaded at all (IIS is suppressing it)
• The error page itself is throwing an unhandled exception (so it fails silently in production)

Start by directly accessing your error route: https://***.com/Error/Error?statusCode=404. If this also shows a blank page or throws an error, fix that first—your error page has a bug (missing resources, permission issues, or code errors that only surface in production).

Fix the httpErrors + Global.asax Conflict #

Using both httpErrors (IIS-level) and Global.asax (ASP.NET-level) error handling can cause unexpected behavior in production if they’re not aligned. Here’s how to sync them:

1. Update web.config for httpErrors #

Use responseMode="ExecuteURL" instead of Redirect—this runs the error page in the context of the original request, avoiding 302 redirects that can trigger 403 errors, and plays nicer with ASP.NET routing. Also, ensure you’re replacing existing responses so IIS doesn’t fall back to default errors:

<system.webServer>
  <httpErrors errorMode="Custom" existingResponse="Replace">
    <remove statusCode="404" subStatusCode="-1" />
    <remove statusCode="500" subStatusCode="-1" />
    <error statusCode="404" path="/Error/Error?statusCode=404" responseMode="ExecuteURL" />
    <error statusCode="500" path="/Error/Error?statusCode=500" responseMode="ExecuteURL" />
  </httpErrors>
</system.webServer>

Also, disable ASP.NET’s customErrors to avoid conflicts:

<system.web>
  <customErrors mode="Off" />
</system.web>

2. Adjust Global.asax Error Handling #

Modify your Application_Error method to avoid duplicate processing (since httpErrors already triggers the error route). Focus on logging or additional logic instead of redundant redirects:

protected void Application_Error(object sender, EventArgs e)
{
    var exception = Server.GetLastError();
    var httpException = exception as HttpException;

    // Log the error first—critical for production debugging
    // Your logging code here (e.g., log to file, database, or monitoring tool)

    // Clear the error to prevent IIS from showing default errors
    Server.ClearError();

    // Only redirect if httpErrors didn't handle it (fallback)
    if (httpException != null)
    {
        int statusCode = httpException.GetHttpCode();
        if (Response.StatusCode != statusCode)
        {
            Response.RedirectToRoute("Error", new { statusCode = statusCode });
        }
    }
}

Fix the 403 Forbidden When Using Redirect #

If you still need to use responseMode="Redirect", the 403 error is almost always a permission issue:

• Allow anonymous access to the Error route: Add this to your web.config to ensure unauthenticated users (who hit 404s) can access the error page:

  <location path="Error">
    <system.web>
      <authorization>
        <allow users="*" />
      </authorization>
    </system.web>
  </location>
  

• Check IIS Authorization Rules: Open IIS Manager → Your Site → Authorization Rules. Ensure there’s an "Allow Anonymous Users" rule, or explicitly allow access to the /Error path.
• Verify App Pool Permissions: Make sure your application pool identity has read access to all files in your site, especially the Error view and its dependencies.

Verify IIS Production Settings #

Double-check these IIS configurations on your production server:

1. Error Page Settings: Go to IIS Manager → Your Site → Error Pages → Edit Feature Settings. Set "Error mode" to Custom errors (not "Detailed errors" or "Detailed errors for local requests only").
2. URL Rewrite Rules: If you’re using URL rewrite, ensure none of your rules are intercepting the /Error/Error route (check for rules that block or redirect paths matching "Error").
3. Request Filtering: Go to IIS Manager → Your Site → Request Filtering. Ensure the /Error/Error path isn’t blocked in the "URL" or "Query Strings" tabs.

Final Testing #

After making these changes:

1. Recycle your application pool in IIS to apply config changes.
2. Test the random URL again (https://***.com/RandomText)—it should load your custom error page.
3. Monitor your logs to confirm errors are being logged correctly.

内容的提问来源于stack exchange，提问作者winterishere