-
Notifications
You must be signed in to change notification settings - Fork 55
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
Fix URL-decoding bug from previous commit #1517
Conversation
Signed-off-by: Johannes Kalmbach <[email protected]>
Signed-off-by: Johannes Kalmbach <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1517 +/- ##
==========================================
- Coverage 92.55% 88.08% -4.48%
==========================================
Files 355 355
Lines 26631 26636 +5
Branches 3575 3576 +1
==========================================
- Hits 24649 23463 -1186
- Misses 1940 1947 +7
- Partials 42 1226 +1184 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Johannes Kalmbach <[email protected]>
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.
Thanks for the fix!
Signed-off-by: Johannes Kalmbach <[email protected]>
…rsing # Conflicts: # src/engine/Server.cpp
Quality Gate passedIssues Measures |
For URL-decoding, now use (the well documented)
boost::urls::parse_origin_form
instead of the (internal and poorly documented)boost::urls::parse_query
because the latter turned out to not unescape+
to space.TODO for a separate PR: When the URL path is malformed, currently a Boost-internal error message is returned, like
leftover [boost.url.grammar:4]
. Instead an exception should be thrown and caught and a proper error message displayed.