Issue #12725 reset match indexes for FilterMappings on setFilterMappings #12734
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 is an alternative fix for PR #12725.
When a user calls
ServletHandler.setFilterMappings(FilterMapping[])
this is like a reset of anyFilterMappings
that may have existed previously, either by a previous call to the same method, or importantly via a call toaddFilterMapping(FilterMapping)
. WhenaddFilterMapping(FilterMapping)
is called, we need to calculate where it should be added, as the servlet spec allows for pre or postpending to existingFilterMappings
. We maintain 2 indexes_matchBeforeIndex
and_matchAfterIndex
to help us determine where to insert the addedFilterMapping
.As
setFilterMappings([FilterMapping[])
is essentially a reset, these 2 indexes need to be reset too.