WIP: option to fall through to middleware chain on source 404 (#248) #390
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.
By default, the proxy handles all requested routes on the given context(s), even if they are 404. This makes sense for routes that are actually handled by the target but there is a use case where it would be useful to be able to fall-through to the middleware chain if the target cannot handle the request. This would allow, for example, for a server’s functionality to be extended by another server.
This merge request adds a
fallthrough
option. When present, any 404 errors fall through to the middleware stack of the server by callingnext()
.Context: #248