Fix URL parsing w/ trailing slash & querystring #1539
Merged
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.
Description
Fix a bug where an URL containing both a trailing slash and a querystring would be incorrectly parsed.
How to reproduce
The following HTTP GET request works fine:
http://localhost:7512/_now?pretty
But not this one without this PR:
http://localhost:7512/_now/?pretty
Both requests are equivalent and should be regarded as identical.
Other changes
Use the WHATWG URL parsing API instead of the legacy (and deprecated) Node.js URL parser.Unfortunately, the latter was much more adapted to URL parsing server-side than the former. 😑
Reverted to the legacy URL API because of: