Fix for nested parameters causing invalid signatures #9
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.
I was trying to submit nested parameters (i.e. object[attribute]=value ) and was getting invalid signatures from our OAuth provider.
After tracing through the code, I saw that already encoded parameters were getting double encoded when submitted to HTTPParameter's getAsQueryString. In my branch, I modified SignatureBaseString's normalizeRequestParameters method to pass in decoded parameters to that method.
This resolved the problem for me. Thought I should pass this information back in case its of any use to you guys.