Skip to content

When form is submitted with no handler, or the handler can't be found, change status to 400/404 #49359

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

Closed
SteveSandersonMS opened this issue Jul 12, 2023 · 0 comments · Fixed by #49340
Assignees
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. feature-full-stack-web-ui Full stack web UI with Blazor
Milestone

Comments

@SteveSandersonMS
Copy link
Member

Currently it returns a 500 which is definitely wrong.

We should change this to either 400 or 404.

cc @javiercn for discussion on which status code.

@SteveSandersonMS SteveSandersonMS added area-blazor Includes: Blazor, Razor Components feature-full-stack-web-ui Full stack web UI with Blazor labels Jul 12, 2023
@mkArtakMSFT mkArtakMSFT added the bug This issue describes a behavior which is not expected - a bug. label Jul 13, 2023
@mkArtakMSFT mkArtakMSFT added this to the 8.0-rc2 milestone Jul 13, 2023
@mkArtakMSFT mkArtakMSFT modified the milestones: 8.0-rc2, 8.0-preview7 Aug 10, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Sep 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. feature-full-stack-web-ui Full stack web UI with Blazor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@SteveSandersonMS @mkArtakMSFT and others