You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
I tried to get HTTPS -> HTTP forwarding working yesterday and it didn't work. After some troubleshooting the bug seems to be in the underlying Nodejitsu http-proxy module if you are trying to forward to a target not running on anything but port 80 or 443.
Seems like they have already fixed it in master, but have not yet pushed a release. Giving you a heads up that you might want to watch for this fix and push an update on your dependency as well. This is a pretty inconvenient bug as SSL termination and forwarding is a pretty common use case for using a reverse proxy.
The text was updated successfully, but these errors were encountered:
Thanks for reporting. It's a weird bug, definitely, but we can't do too much until they release a new patch version, so let's wait for a while. I'll have an eye on this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I tried to get HTTPS -> HTTP forwarding working yesterday and it didn't work. After some troubleshooting the bug seems to be in the underlying Nodejitsu http-proxy module if you are trying to forward to a target not running on anything but port 80 or 443.
http-party/node-http-proxy#915
Seems like they have already fixed it in master, but have not yet pushed a release. Giving you a heads up that you might want to watch for this fix and push an update on your dependency as well. This is a pretty inconvenient bug as SSL termination and forwarding is a pretty common use case for using a reverse proxy.
The text was updated successfully, but these errors were encountered: