-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Blazor Web App is missing an error page #49853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A few things to note about the existing Razor Pages based error page:
|
Making this work end-to-end will be nontrivial. I've filed an issue with details at #50287. We might decide it's unwise to rush that for .NET 8. In the meantime, let's use this issue to track what we're doing for the error page in the project template in .NET 8, since that's literally what the issue title is about. Options for .NET 8
I'm changing the labels to make this reappear in triage. |
also cc @danroth27 |
…Applications (#50550) ## Description Adds support for Error pages to Blazor Web application. * Includes a small change to the ExceptionHandler middleware to support Blazor Web scenarios. * Includes a change in Blazor Web to account for error handling scenarios and disable streaming rendering and interactivity. * Includes changes to the Blazor Web template to add an Error page similar to the one in MVC and Razor pages templates. Fixes #49853, #49854 ## Customer Impact * Customers won't be able to see errors in Blazor Web Applications without having to rely on MVC or Razor Pages for it, which adds significant complexity to their setup. ## Regression? - [ ] Yes - [X] No ## Risk - [ ] High - [X] Medium - [ ] Low * If customers hit any issues, we will be able to tell them to simply remove the ErrorPage.razor page from their projects. Luckily, we will have a little bit of time to address any critical feedback in case such comes up. As of right now, this change has been validated and it works. ## Verification - [X] Manual (required) - [X] Automated ## Packaging changes reviewed? - [ ] Yes - [ ] No - [X] N/A
When deployed to production a Blazor Web App will redirect server errors using
app.UseExceptionHandler("/Error");
. But there is nothing listening at /Error so you end up with a 404. Typically the error page is handled by a Razor Page, but in a Blazor Web App it should be a Blazor component page.The text was updated successfully, but these errors were encountered: