-
Notifications
You must be signed in to change notification settings - Fork 375
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
fix: undefined HTTP method handlers not responding with 405 #1041
Conversation
composeMiddleware([ | ||
apiRoutes, | ||
inlineServerFunctions, | ||
apiRoutes, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without changing the order, requests for server functions will be mistakenly handled by wildcard routes (like 404) that now have a handler for all methods.
This can be reproduced in the latest version 0.3.5
by adding a POST method handler to the [...404] page. It will break server functions.
Thank you for all your work on this. However, in setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed in mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience. See #1139 for more details. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The docs state the following:
This is not the case.
What is the new behavior?
404 Page
[...404] wilcard route should look like this if it's desired to return 404 for all HTTP methods otherwise 405 will be returned.
Other information