Return the path in error handling

[gurkantuna]

I handle the errors very well throughout the project as described in this section of the document. Personally, I prefer just one controller for errors.

Startup.cs

app.UseStatusCodePagesWithRedirects("/Error?status={0}");

ErrorController

[ResponseCache(Duration = 0, Location = ResponseCacheLocation.None, NoStore = true)]
public IActionResult Index(int? status) {

    var errorViewModel = new ErrorViewModel {
        RequestId = Activity.Current?.Id ?? HttpContext.TraceIdentifier
    };

    var exceptionHandlerPathFeature = HttpContext.Features.Get<IExceptionHandlerPathFeature>();
   //handle the error
}

It returns the HTTP status code with status variable , but I want to return the previous request path as well. I was writing a new middleware from the UseStatusCodePagesWithRedirects extension, but the controller cannot catch the error because I changed the original pattern to another one. eg.code={0}&path={1} . I try different features in HttpContext but they only return status code normally. To put it simply, I want to handle referrer uri to the error controller.

Feature Request

It should be one more query string named for example path or something else and it shuold returns the previous uri in the UseStatusCodePagesWithRedirects extension.

Should be

app.UseStatusCodePagesWithRedirects("/MyStatusCode?code={0}&path={1}");

In this way, the path can handle in the controller as follows.

public IActionResult Index(int? status, string path) {

[Tratcher]

Note that UseStatusCodePages* handles more than error conditions, it would handle any response that did not provide a body. Responses without bodies are more common in Web API scenarios.

Have you tried using UseStatusCodePagesWithReExecute instead of UseStatusCodePagesWithRedirects? That behaves like UseExceptionhandler and preserves the request path in a feature as described here:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-5.0#usestatuscodepageswithreexecute

[gurkantuna]

@Tratcher Thanks for your suggestion. You are absolutely right, it was my fault 🙈 I had tried the 'UseStatusCodePagesWithRedirects' you pointed out before the post above, turns out I tried to handle it with type IExceptionHandlerPathFeature and the future was normally null. I looked the paramaters again after your suggestion and I replaced it with IStatusCodeReExecuteFeature which is the correct type. Then future is not null and the OriginalPath is returns the path.

Thanks for your help 🍻