fix: do not partial match url params extraction #22281
Open
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:
Fix for #16137.
Custom Action Dimensions have an option to automatically extract values from the URL Search Parameters. As mentioned in the docs, it does not allow using Regex because it's supposed to be a "simple" match. One would assume it's doing a simple check to fetch the exact match for the URL parameter.
However, it's actually constructing a partial match with the regex
\?.*pattern=([^&]*)
. This works fine in most cases, but if thepattern
is included in another pattern's word ending, this regex picks that up instead.So imagine trying to extract the
type
parameter from the URLIt should match
type=foo
and returnsfoo
in theory, but current regex actually matchestype=baz
at the end fromcontenttype=baz
because the regex is only searching for a parameter that ends with the specified pattern, in this casetype
. To fix this, we know that valid URLs don't have?
or&
unless they are for search params (as they should be URL encoded otherwise), we can construct the regex[?&]pattern=([^&]*)
instead to make sure the exact pattern is matched in the URL.Review