-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Not found error with Express route but it works! #1523
Comments
I don't get it, I would check the network tab. Not Found on the base route shows up because there isn't a favicon, but that's typical if you don't handle that case. No issue other than the favicon on the base route for me. |
Not. It's not the favicon the problem. Try to go back and forward in the browser! |
It looks like you are adding a middleware on all routes, to call 404? The error handler in Express is only invoked when it has 4 arguments (err, req, res, next). Or you can add a catchall to the app stack, like link mentioned below. Quick glance, may not be correct. https://stackoverflow.com/questions/11500204/how-can-i-get-express-js-to-404-only-on-missing-routes |
I found this problem: https://stackoverflow.com/questions/51826711/express-js-error-handler-doesnt-work-if-i-remove-next-parameter But now the error handler with
Reproducible with these steps:
|
Closing this for now as it's quite old and it seems to be an error in how you're using express. If you still need help feel free to reopen and let us know updated steps on how to reproduce it! |
I have a problem with my
express
app:https://glitch.com/edit/#!/enthusiastic-velociraptor
When I navigate to
GET
/graphql
it gives me Playground but in console I have aNot found
Why?
Reproducible with these steps:
The text was updated successfully, but these errors were encountered: