-
Notifications
You must be signed in to change notification settings - Fork 2k
Urgent: Fix breaking bug on url joining resulting in paths like ///path
.
#699
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
Conversation
Yep - working on that right now, just figured I should get the fix in ASAP. On Sep 12, 2014, at 12:57 PM, Arnout Kazemier [email protected] wrote:
|
Yes, it should, but I can't release a new version anyways as I don't have publish rights (which is why I haven't merged it in yet either) |
Added OS-agnostic url join helper.
Ok. I have amended the commit to include a test. On Sep 12, 2014, at 1:01 PM, Arnout Kazemier [email protected] wrote:
|
Urgent: Fix breaking bug on url joining resulting in paths like `///path`.
Thanks a lot for contribution. Will make sure that is out as fast as possible. |
Pubished as |
@STRML thanks a ton for the fix. I go and try and fix a windows bug and I do something terrible xD. Im very curious of the case that caused the path to be prefixed with |
@jcrugzz It could happen two ways, possibly resulting in I had been using a target as a deep path, something like Understandably there shouldn't be a trailing slash in the target, but it is very common for there to be a leading slash in the proxied path (from req.url), and this commit broke that case as well with a double slash. |
Thanks for quickly responding to this issue. |
This commit can completely break production apps and this or a similar hotfix needs to be deployed ASAP.