I had missed the 404 pages in the documentation! (Ooopsie), but just in case anyone else stumbles across this post and finds it's useful: -

I've configured appsetting.json with XPath as I would previously. I'm a huge uSync fan and when restoring a website with uSync, to my knowledge, the page IDs may change; so I've tended to use XPath for custom error pages to save having to adjust IDs after a restore.

To serve a default 404 page for each language this is working for me...

  "Umbraco": {
    "CMS": {
      "Content": {
        "Error404Collection": [
          {
            "ContentXPath": "//rootNode//errorPageFolder[@nodeName='Error']//errorPage[@nodeName='Page Not Found']",
            "Culture": "default"
          }
        ]
      },
    ...

To serve different 404 pages for specific languages this is working for me...

"Umbraco": {
    "CMS": {
      "Content": {
        "Error404Collection": [
          {
            "ContentXPath": "//rootNode//errorPageFolder[@nodeName='Error']//errorPage[@nodeName='Page Not Found']",
            "Culture": "default"
          },
          {
            "ContentXPath": "//rootNode//errorPageFolder[@nodeName='Error']//errorPage[@nodeName='Page Not Found2']",
            "Culture": "en"
          },
          {
            "ContentXPath": "//rootNode//errorPageFolder[@nodeName='Error']//errorPage[@nodeName='Page Not Found3']",
            "Culture": "cy"
          }
        ]
      },
    ...

I'm still looking for a way to serve a custom 500 error page that I can keep in the CMS. So still playing and still really enjoying V9 so far :)

Hey Andy!

Ironically, the above you used did not work for me on the RC version of Umbraco V9, however I used the ContentLastChanceFinder for the 404 and that worked - https://our.umbraco.com/Documentation/Reference/Routing/Request-Pipeline/IContentFinder-v9

Any luck with the 500 and other error pages? I've tried the status code implementation, but can't manage to his the custom error handles as suggested here -https://docs.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-3.1

Thanks!

Hey Javz,

I haven't found of a way to do 500s with an Umbraco 9 setting yet, but I have got them working with some middleware. The very first part of my middleware pipeline starts with this: -

if (env.IsDevelopment())
{
   app.UseDeveloperExceptionPage();
}
else
{
   app.UseExceptionHandler("/error/internal-server-error/");
   app.UseHttp200StatusCodesForExceptions();
 }

The string in UseExceptionHandler middleware is the path to a page I have published in Umbraco and the second line is another little bit of middleware to change the status code from a 500 to a 200, just in case any fuzzers are poking around for errors :)

I've not had chance to look at different routes for different languages just yet, nor have I had chance to look at any other status codes with UseStatusCodePages(), but I'm hoping to find time to have another play this week. If I get any further, I'll post here.

Hope this is helpful.

Hi Javz,

Yep, I just did some route hijacking to throw a Not Implemented Exception to see if it worked. Here's what I have in my controller: -

public class ContentPageWithGridLayoutController : RenderController
{
    public ContentPageWithGridLayoutController(
        ILogger<ContentPageWithGridLayoutController> logger, 
        ICompositeViewEngine compositeViewEngine, 
        IUmbracoContextAccessor umbracoContextAccessor) 
    : base(logger, compositeViewEngine, umbracoContextAccessor) { }


    //
    // RenderController Implementation

    public override IActionResult Index()
    {
        throw new NotImplementedException();
    }
}

I wonder if its not detecting that you're in the Production Environment. What happens if you change the beginning of your Middleware in Startup.cs from this: -

  public void Configure(IApplicationBuilder app, IWebHostEnvironment env, ILogger<Startup> logger)
  {
   if (env.IsDevelopment())
   {
      app.UseDeveloperExceptionPage();
   }
   else
   {
      app.UseExceptionHandler("/error/internal-server-error/");
   }
   ...
 }

To this: -

 public void Configure(IApplicationBuilder app, IWebHostEnvironment env, ILogger<Startup> logger)
  {
     app.UseExceptionHandler("/error/internal-server-error/");
     ...
  }

This will mean we'll lose the developer exception pages, because we're always returning an exception page now, but if it works, that gives us a clue that the problem is with the environment rather than the middleware. :)

I've done some experimenting and found that, if you're proxying through IIS like on Umbraco Cloud, the old approach of controlling error responses there still works, so your web.config file becomes:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\UmbracoProject.dll" stdoutLogEnabled="false" stdoutLogFile="\\?\%home%\LogFiles\stdout" hostingModel="inprocess" />

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

A few things to note:

• it supports status codes other than 404/500, as with 400 shown here. Add as many as you need.
• the route can be an Umbraco page, a static file, or probably an MVC action (I didn't try the last one)
• if you have app.UseExceptionHandler("/errors/500") that path is used in preference to the one in web.config
• if you have Error404Collection configured in appsettings, web.config takes precedence over that (I haven't tried the LastChanceContentFinder approach)
• dotnet run on your local machine isn't usually behind an IIS proxy, so if you try this there it probably won't work

On a v8 project you could make this config change when deploying to Umbraco Cloud by using web.live.xdt.config file. That doesn't appear to work any more, so I'm not yet sure how to deploy this to Umbraco Cloud. I've tested it by editing the file manually in Kudu.

In v8 and below web.config was used by three layers, the web server (IIS), ASP.NET, and Umbraco. With v9, Umbraco and ASP.NET don't use it any more, and while you still have a web server it doesn't have to be IIS, so that's why you've heard that it's gone away. However if you are using IIS then web.config still has a role to play.

app.UseExceptionHandler("/errors/500") was done exactly as Andy describes. It just worked for me, but I wanted to handle the other codes too so I kept looking. I was actually using it with a static HTML file in the wwwroot folder so my line was app.UseExceptionHandler("/500.html"), but all the examples I saw online show it should work with an MVC route too.

There is a way to deploy config like this on Cloud - name your transform file Web.Release.config and put it in the src\UmbracoProject folder (or wherever you changed the reference in the .umbraco file to point to).

The #h5yr goes to @c9mbundy on this Github issue.

I'm trying to get the custom error page for HTTP status code 500 to work using UseExceptionHandler, but while it works and displays the correct page, the HTTP status code for the response is 200 whereas I would like it to be 500 (so we can pick up any errors in our analytics logs as well).

The Configure method in our Startup.cs looks like this:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();
    }
    else
    {
        app.UseExceptionHandler("/500.html");
    }

    app.UseUmbraco()
        .WithMiddleware(u =>
        {
            u.UseBackOffice();
            u.UseWebsite();
            u.UseAzureBlobMediaFileSystem();
        })
        .WithEndpoints(u =>
        {
            u.UseInstallerEndpoints();
            u.UseBackOfficeEndpoints();
            u.UseWebsiteEndpoints();
        });
}

If I intercept the response for a failing request (i.e. be throwing an exception on the homepage template) between the UseExceptionHandler call and the app.UseUmbraco call I can see that the response status code at that point is set to 500:

app.Use(async (context, next) =>
{
    Debug.WriteLine(context.Response.StatusCode);

    await next();
});

Could it be that the Umbraco pipeline somewhere changes the response status code back from 500 to 200? And if so, how could we prevent that from happening?

is working on a reply...