-
Notifications
You must be signed in to change notification settings - Fork 132
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
Problem behind a Proxy with Tunnel #194
Comments
Fixed in follow-redirects/follow-redirects#118. |
Hi. Sorry but I'm beginner in using GitHub |
The bug you have identified above, is—as you write—a problem in the follow-redirects module. Since the bug was not reported with follow-redirects, I could not fix it. Yesterday I got notified about this issue in follow-redirects/follow-redirects#118, and I fixed it today. So if in the future you find bugs in other modules, you might want to report them in those other modules so that they can get fixed faster. |
You're right. |
Hi,
We found an issue while using your module behind a proxy.
In your code, in the function proxy, you register proxyTunnel to the connect event.
But in the follow-redirects module, the connect event is not managed:
Therefore, you never receive the connect event and the code is never triggered.
To fix this, I just added the following lines in the node-modules/follow-redirects/index.js file to manage the connect event.
I know the problem is not in your module.
It's just to let you know.
Regards & Thanks for this module !
The text was updated successfully, but these errors were encountered: