Add support for registering handlers for different 404 routes #2217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for registering handlers for 404 routes. Echo instance and group has now method
RouteNotFound(path string, h HandlerFunc, m ...MiddlewareFunc) *Route
which registers handler for given path. Path supports any/path parameters and can be static (which is little bit silly but we still support it)
Custom 404 handler has priority in router over global 404 handler and 405 handling logic.
Example:
so you would have 2 404handlers in this example:
/*
/images/*
Routing performance is not significantly affected by this feature.
Benchstat between current master branch and this branch.