Empty query string ("/?") causes route match to fail #937
Conversation
This file contains hidden or 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
ryanflorence
added a commit
that referenced
this pull request
Mar 21, 2015
Empty query string ("/?") causes route match to fail
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
/and/?aroute to the same place, but/?won't match any route and will trigger not found. This issue is not experienced withHistoryLocationin the browser because when the URL ends with?thenwindow.location.search == ""thereby dropping the question mark; however when usingreq.urlin Node.js the?is not automatically dropped.I've fixed the issue via a tweak to the regex, and added a relevant test.
I'm not sure if we need to change
extractQueryin PathUtils to return false ifmatch[1].length === 0?