-
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
Issues with Multiple Reverse Proxy #93
Comments
Any one had looked into this issue? |
Just confirmed this bug is only in npm version |
@nazarhussain you can install the pre-release that was published in November. It was tagged as |
I've just released v2.0.0-1 as the |
@rmg will check it on Monday and let you know. |
@rmg Yes it works. Thanks for working on this issue. Here is node repo that contains minimal code to test this issue. https://github.com/nazarhussain/foreman-multi-proxy-test/ |
The test setup is based on the behaviour described in #93, but with the required modifications to support testing without using any fixed ports.
The test setup is based on the behaviour described in strongloop#93, but with the required modifications to support testing without using any fixed ports.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I am facing problem with multiple reverse proxies. It is not functioning as per described in Readme.
I have following Procfile.
Now I run it with:
And the output that came out and cause error onward.
As you can see cleary there are two issues:
It seems something is clearly broken. Please help me out to troubleshoot the issue.
Thanks.
The text was updated successfully, but these errors were encountered: