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.
As consequence of #472, it's now possible to have following custom-data:
and following configuration for HeaderLookup:
that aims to retrieve the
extra-field
of the authenticated user. However if the authenticated user isbob
(= value ofX-AUTH-USER
header isbob
), bob cannot retrieve data entries bob-bananas and bob-pearls.This PR aims to solve this by introducing
pathRegExp
parameter that extracts specified part of the path and appends it to the custom-data key, when retrieving data. Let's change the configuration of the HeaderLookup toNow when
header("X-AUTH-USER") = "bob"
and requestpath = /bananas
, the HeaderLookup retrieves the custom-data entrybob-bananas
.