IIS7 web server custom errors - works on local but not when published to production

Question

I am building a new site with custom error pages. I have setup my web.config, and have all of my pages setup.

When I run locally, and force errors (page not found i

Answer 1

Does this help?

I wonder if you also have to register the paths to the custom errors that way as well.

Answer 2

By default IIS7 intercepts HTTP status codes such as 4xx and 5xx generated by applications further up the pipeline.

You can tell IIS to just pass through the existing response without replacing it with its own error page:

<configuration>
  <system.webServer>
    <httpErrors existingResponse="PassThrough" />
  </system.webServer>
</configuration>

For more information see:

HTTP Errors <httpErrors>