Skip to content
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

Handle non-trailing slashes correctly #1512

Merged

Conversation

hekike
Copy link
Member

@hekike hekike commented Oct 9, 2017

Issues

Closes:

#1464
#1478

Non-trailing slash leads to incorrect routing match (and parameter parsing).

Changes

Fix router regexp matching with non-trailing slash(es)

@retrohacker retrohacker merged commit ac1eec5 into restify:next Oct 9, 2017
hekike added a commit that referenced this pull request Jan 30, 2018
* router - remove do not merge double slashes by default
* use server.pre(restify.plugins.pre.dedupeSlashes()) to deal with double slashes
* refactor test to cover multiple slashes cases
hekike added a commit that referenced this pull request Feb 23, 2018
* router - remove do not merge double slashes by default
* use server.pre(restify.plugins.pre.dedupeSlashes()) to deal with double slashes
* refactor test to cover multiple slashes cases
hekike added a commit that referenced this pull request Mar 13, 2018
* router - remove do not merge double slashes by default
* use server.pre(restify.plugins.pre.dedupeSlashes()) to deal with double slashes
* refactor test to cover multiple slashes cases
hekike added a commit that referenced this pull request Mar 20, 2018
* router - remove do not merge double slashes by default
* use server.pre(restify.plugins.pre.dedupeSlashes()) to deal with double slashes
* refactor test to cover multiple slashes cases
hekike added a commit to sfaizanh/node-restify that referenced this pull request Mar 27, 2018
* router - remove do not merge double slashes by default
* use server.pre(restify.plugins.pre.dedupeSlashes()) to deal with double slashes
* refactor test to cover multiple slashes cases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants