Fix query parameters encoding in rewritten target requests #205
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.
Fixes request rewriting when query parameters contain a value that matches a percent-encoded value (e.g.
%2F).Previously, such values were not encoded when adding query parameters to the rewritten request, as the method used internally by
JerseyUriBuilder.queryParamto encode values (UriComponent.contextualEncode) is recognizing percent-encoded values to avoid double-encoding. This led to changing the original request, and subsequently the remote denying the request withSignatureDoesNotMatcherror.To fix this, we can encode all query parameter values before passing them to the URI builder, as we know that they require encoding.