[TT-3158] Fix for quantity match expressions on method transform paths #3548
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.
Description
Fixes the behavior described in #3547
Related Issue
#3547
Motivation and Context
Before this change, a path like
/my/path/(?:[0-9a-fA-F]{8})$
would be treated as/my/path/(?:[0-9a-fA-F]([^/]*))$
, which causes unexpected behavior onurl_rewrites
,method_transforms
andtransform_headers
inextended_paths
How This Has Been Tested
In order to test this the bellow API can be loaded (make sure to create a new webhoo on the target_url).
The request
should behave the same as this request
API Definition
Checklist
fork, don't request your
master
!master
branch (left side). Also, you should startyour branch off our latest
master
.go mod tidy && go mod vendor
go fmt -s
go vet