fix: url match logic of http server #199
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.
Currently, both
"/foo"
and"/bar/foo"
are matched to/\/foo/
and the later is used because it is longer than the former. This is correct but strange behavior for url routing. I changed logic of evaluation for priority of matches:With this logic,
"/foo"
is prior to"/bar/foo"
because the former matched to/\/foo/
at index 0."/foo/bar"
is prior to"/foo"
because the former has longer match than the later.