-
Notifications
You must be signed in to change notification settings - Fork 388
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: return 404 when server function not found #1775
Conversation
|
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
More templates
commit: |
Thanks a lot for this PR, @loetjvr Looking at the code and our compliance tasks, I'd like to ask for a few additional things if you're ok with it:
Let me know your thoughts if you don't agree. Cheers 🏆 |
More than happy to make the changes @atilafassina Also on point number 4, what does this entail? I updated the pr title, should I update somewhere else as well? |
ece20d9
to
0aa90bc
Compare
0aa90bc
to
cbea1b8
Compare
That's entirely on us, @loetjvr Now that your PR reached Thanks a lot for your work!! 🏆 |
fixes #1779
What is the current behavior?
Currently server functions calls are expected to always provide the correct id and name. However in our use case we have had bots that try to access older id and name combinations which results in a 500 error.
What is the new behavior?
This change treats not found server functions with a 404 response so that it provides better logging results in case an older or wrong id is being accessed directly.