app.UseExceptionHandler and ExceptionHandlerMiddleware.cs

[marcdumont3000]

I would like to know if it's possible to localize or set back the culture in the context when an Exception occure using app.UseExceptionHandler("/{culture}/error") in the config startup ?

Or is there other ways to achieve that?

this is part of the Assembly Microsoft.AspNetCore.Diagnostics

thanks
Marc

[davidfowl]

No this doesn't work. What are you trying to achieve?

[BrennanConroy]

Is using the culture info in your error.cshtml not good enough?

[marcdumont3000]

Just to give more context.....We are using localize routes like this:

Pattern: /{culture}/home/index and the default culture is en
Valide routes:
/en/home/index
/fr/home/index

So when an error occurs, the user is automatically redirected to the error page... I have this setup in the startup/configure:
app.UseExceptionHandler("/error");

But, every time the user gets redirected to the error page..the culture info gets reset to the default... the context for the culture is not kept when we hit the error page.

So what can we do to fix this issue?
thanks

[BrennanConroy]

You can grab the original path from the features in your error page, see the docs at https://docs.microsoft.com/aspnet/core/fundamentals/error-handling?view=aspnetcore-3.1#access-the-exception-1

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[davidfowl]

I forgot to follow up on this issue. It's difficult to do this today and we need some tweaks to the error page middleware to handle it. Ideally you would be able to re-execute the pipeline with a callback to customize the request.