dotnet / dotnet/AspNetCore.Docs

UseStatusCodePagesWithReExecute method original context handling unclear

Open
#34,070 0 comments 0 reactions 1 assignee Claimed by @tdykstra View on GitHub
:watch: Not Triaged aspnet-core/svc fundamentals/subsvc Source - Docs.ms
Dominant language
C#
Stars
13.1k
Forks
24.6k
Avg merge
1d 2h
Merged PRs (30d)
109

Description

### Description

Example, on this same page there is a point to mention:
> For the [UseExceptionHandler(IApplicationBuilder, String)](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.builder.exceptionhandlerextensions.useexceptionhandler#microsoft-aspnetcore-builder-exceptionhandlerextensions-useexceptionhandler(microsoft-aspnetcore-builder-iapplicationbuilder-system-string)) overload that is used in templates, only the request path is modified, and the route data is cleared. Request data such as headers, method, and items are all reused as-is.

However for the UseStatusCodePagesWithReExecute extension method it does not clarify this point. Specifically I was trying to verify how to see the original http method and referrer during the custom handling. Through trial and error I was able to verify that the http method and the referrer are preserved and I could simply get the values from the HttpContext.Request. This documentation would be incredibly helpful with this update.

### Page URL

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-8.0

### Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/error-handling.md

### Document ID

38515dfb-91a5-b395-db9d-084bbaf095c8

### Article author

@tdykstra

[Related Issues](https://github.com/dotnet/AspNetCore.Docs/issues?q=is%3Aissue+is%3Aopen+38515dfb-91a5-b395-db9d-084bbaf095c8)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.