New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #20943: Rudder incorectly parse URL with a '+' in the path into spaces #4217
Fixes #20943: Rudder incorectly parse URL with a '+' in the path into spaces #4217
Conversation
PR updated with a new commit |
PR updated with a new commit |
// https://stackoverflow.com/questions/1634271/url-encoding-the-space-character-or-20/29948396#29948396 | ||
(req.path.partPath.map { e => | ||
// change back spaces into "+" | ||
ApiPathSegment.Segment(e.replaceAll(" ", "+")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if there is a space intended ? can we try both ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we never want spaces in api path. This is very uncomon and a source of problems.
(that's not for the query parameters, just the path)
This PR is not mergeable to upper versions. |
OK, squash merging this PR |
fc9c368
to
0c794c1
Compare
https://issues.rudder.io/issues/20943
When on API, correct back "+" that were changed inot " " by lift
Also correct tests that were not returning the correct node :/