Skip to content

fix(Express Router): breaking unmatched paths (non proxy routes)#98

Merged
chimurai merged 1 commit intomasterfrom
express-sub-route-fi
Aug 11, 2016
Merged

fix(Express Router): breaking unmatched paths (non proxy routes)#98
chimurai merged 1 commit intomasterfrom
express-sub-route-fi

Conversation

@chimurai
Copy link
Copy Markdown
Owner

@chimurai chimurai commented Aug 7, 2016

fixes #94

req.url get rewritten even for non proxy routes.

Fix:
Only rewrite req.url when proxy routes matches.

@coveralls
Copy link
Copy Markdown

coveralls commented Aug 7, 2016

Coverage Status

Coverage increased (+0.006%) to 99.373% when pulling 1c3df2e on express-sub-route-fi into 306fdd4 on master.

@chimurai chimurai force-pushed the express-sub-route-fi branch from 1c3df2e to 2d5dff4 Compare August 7, 2016 20:53
@coveralls
Copy link
Copy Markdown

coveralls commented Aug 7, 2016

Coverage Status

Coverage increased (+0.006%) to 99.373% when pulling 2d5dff4 on express-sub-route-fi into 306fdd4 on master.

@chimurai chimurai force-pushed the express-sub-route-fi branch from f43b986 to 7deb5c3 Compare August 11, 2016 20:47
@coveralls
Copy link
Copy Markdown

coveralls commented Aug 11, 2016

Coverage Status

Coverage increased (+0.006%) to 99.373% when pulling 7deb5c3 on express-sub-route-fi into 306fdd4 on master.

@coveralls
Copy link
Copy Markdown

coveralls commented Aug 11, 2016

Coverage Status

Coverage increased (+0.006%) to 99.373% when pulling 7deb5c3 on express-sub-route-fi into 306fdd4 on master.

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.

Doesn't seem to recognize non proxy routes (express)

2 participants