Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Blazor] NavigationManager.NotFound or equivalent API for SSR #58816

Open
javiercn opened this issue Nov 6, 2024 · 0 comments
Open

[Blazor] NavigationManager.NotFound or equivalent API for SSR #58816

javiercn opened this issue Nov 6, 2024 · 0 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-ssr triaged
Milestone
.NET 10 Planning

Comments

@javiercn
Copy link
Member

javiercn commented Nov 6, 2024

Lack of NavigationManager.NotFound() or equivalent API for triggering NotFound on Blazor applications. This would trigger a 404 response on SSR scenarios that would render the NotFound page/component and on InteractiveScenarios it would signal any registered callback (the router) the equivalent situation (which would trigger the render)
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Nov 6, 2024
@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-ssr labels Nov 7, 2024
@mkArtakMSFT mkArtakMSFT added this to the .NET 10 Planning milestone Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-ssr triaged
Projects
None yet
Milestone
.NET 10 Planning
Development

No branches or pull requests
2 participants
@javiercn @mkArtakMSFT