fix: handle encoded slashes for url parameters - fixes #552 #553
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I can take a look at it in hopefully tonight or tomorrow. Thanks for the contribution and for testing it :) |
|
I added some additional testing, but did get this merged in. Thanks so much! 765887d |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Caveat: technically, this introduces a backwards incompatible change, for instances where in the request URL (regular) slashes are encoded. I'd guess, that this is not relevant in regular setups and even though this was gracefully handled before, this change is neccessary to assure path params can contain encoded slashes.