i don't think your code is right... remove your <error404> node

and just uncomment the <errorPage culture="default">1119</errorPage>

that should get you up and running.

Hey bob.

I have tried this one too, still doesn't work..

    <errors>
      <errorPage culture="default">1119</errorPage>
    </errors>

Any ideas of what why my page won't accept this one?

I just get the default 404 iis error pages. But my extensionless website works very well beside this problem :)

Daniel,

What you posted looks the same as the configuration we are using on a Umbraco 4.0.0, Windows 2003 site:

<errors>
      <!-- the id of the page that should be shown if the page is not found -->
      <!--        <errorPage culture="default">1</errorPage>-->
      <!--        <errorPage culture="en-US">200</errorPage>-->
      <error404>1234</error404>
</errors>

Have you checked to see in your web.config if you maybe have the customErrors defined somewhere like this:

<customErrors mode="On">
  <error statusCode="404" redirect="My404ErrorPage.aspx" />
</customErrors>

I think the web.config settings will overrule Umbraco's settings (I haven't tested this). customErrors is off on my install and then your first example works fine.

I'm also having the same issue: No 404 handling on site with:

- Umbraco 4.0.2.1
- Windows Server 2008 x64
- IIS 7 under Integrated Pipeline

    <errors>
      <!-- the id of the page that should be shown if the page is not found -->
      <!--        <errorPage culture="default">1</errorPage>-->
      <!--        <errorPage culture="en-US">200</errorPage>-->
      <error404>1177</error404>
    </errors>

Hopefully what solves the 404 issue solves another issue I'm having: http://our.umbraco.org/forum/getting-started/installing-umbraco/4237-Touch-Webconfigapplication-restart-=-first-request-500---Internal-server-error

Changing the EnableSplashWhileLoading setting to False solves my initial request 500 error:

    <!-- Show the /config/splashes/booting.aspx page while initializing content -->
    <EnableSplashWhileLoading>False</EnableSplashWhileLoading>

but 404 handler still not happening.

However, switching to Classic Pipeline makes it work. Therefore, the issue definitely has to do with running under Integrated Pipeline.

Thank you for sharing information everyone, especially you Ted. Cause i can see you got the same setup and problem.

My solution is on a hosted server, so changing the pipeline is a bit difficult. Did you change the pipeline, and is there any performance downgrade on that action?

I am running everything on Integrated Pipeline, and with the asp.net 3.5 web.config. No problems here.

Daniel: I'm using integrated pipeline, and can easily switch it to classic and have no issues. However, for other requirements I need to run integrated.

Sebastiaan: Argh. That doesn't make sense. Umbraco is the only 3.5 app that I've had this issue with...

Who else is running integrated pipeline and is having this issue with Umbraco?

For more information on the wider spread issue, see my other post at http://our.umbraco.org/forum/getting-started/installing-umbraco/4237-Touch-Webconfigapplication-restart-=-first-request-500---Internal-server-error

and

• http://stackoverflow.com/questions/434272/iis7-overrides-customerrors-when-setting-response-statuscode
• http://forums.iis.net/t/1146653.aspx
• http://learn.iis.net/page.aspx/267/how-to-use-http-detailed-errors-in-iis7/

Sebastiaan: are you running it under Windows Server 2008 x64?

IIS7 integrated pipeline and errors item posted to CodePlex: http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=24786.

Solved. Please see Please see http://www.andornot.com/about/developerblog/2009/10/errors-sending-right-message.aspx for more information.

http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=24786

But should documented:

Windows Server 2008 with IIS7 by default hijacks responses with status codes apart from 200 OK and replaces the response with the specified built-in error pages. This does not apply on Vista or Windows 7, and I assume many hosts switch this behaviour by default. Therefore, only a smaller segment of users would typically run into this.

As setting the Response.TrySkipIisCustomErrors = true; everywhere is not very feasible, there is a work around that appears to work: flip a switch in your applicationHost.config file that passes your response through without IIS hijacking it. This is the sledgehammer approach, but works as required for Umbraco as it goes back to for i.e. IIS 6 default approach. Non-200 status code responses now are handled within Umbraco without being hijacked (i.e. NotFoundHandlers, booting screens, etc.).

    <location path="Site Description">
        <system.webServer>
            <httpErrors existingResponse="PassThrough" />
        </system.webServer>
    </location>

Thanks to Fabian Heussser's comment on Rick Strahl's post that helped with this (http://www.west-wind.com/weblog/posts/745738.aspx#829305).

That fixed my problem... just added <httpErrors existingResponse="PassThrough" /> to my web.config under <system.webServer>

Danka!

Nice, IIS 7 seems to have a lot of hidden options to make it do what you want... not sure why these options aren't in there by default.

Is it possible to specify a 404 by recursive property? (For when you have multiple sites in one installation).

Martin

Thanks Ted

Just had the same problem on an ancient 4.0.3 install, your tip worked perfectly :-) 

is working on a reply...