-
Notifications
You must be signed in to change notification settings - Fork 322
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
Customize route failure response #10
Comments
Also note that currently no middleware is applied to this fallback 404 responder. Worth thinking if that's what we want. |
@aturon Currently working on this. Thought process is as follows: We can allow user's to specify a default handler. This function will run if no route match is found. The other thing i'd like to implement is an error handler akin to actix-web's, see here. I think between the two of them, that should give a pretty good start for handling any kind of failures that can happen during a request :) Let me know what you think! |
Right now, Tide always returns an empty 404 response when there is no route match. This should be customizable.
Possibly blocked by #5, if we want to use the same configuration mechanism for this.
The text was updated successfully, but these errors were encountered: