Fixes routing issue with path filters and static uri #3747
Merged
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.
The problem arises from when MvcUtils.setRequestUrl is called depending on if the route was created via config, using
http(uri)or having it set in a before filter.To fix this, the uri is now always set in a before filter and the
http(uri)methods are deprecated in favor of a BeforeFilterFunctions.uri() method.A new DefaultHandlerSupplier was created to use an updated HandlerDiscoverer.Result that has fields for lowerPrecedenceFilters and higherPrecedenceFilters as the
http()family of Handler methods need associated filters.This results in a more consistent handling of the request url attribute.
Existing methods and constructors are deprecated.
TODO: update the docs to use the new
urifilter.Fixes gh-3736