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
I spent quite a lot of time trying to getting a websocket proxy working on 0.10 before digging through the issues and realising 0.10 isn't supported. Maybe it would be worth adding a note to the readme that node-http-proxy is only compatible with 0.8?
The text was updated successfully, but these errors were encountered:
Version 0.10.4
* tag 'v0.10.4':
[dist] Version bump. 0.10.4
[dist] Bump dependencies.
added option for eventlistenerCount(max)
added unlimited listeners to the reverproxy event obj.
[fix] Optimize fix for `x-forwarded-for-port`.
determine x-forwarded-port from host header
[dist minor] 2 space indents next time @samalba
Prevent headers to be sent twice
Put the arguments the right way around in the README.
Put the arguments the right way around in emitter.
Update the README to describe middleware err handler.
Emit middlewareError when on middleware error.
Fix for http-party#458. Host header may cause some sites not to be proxyable with changeOrigin enabled
[fix] remove old reminescence
Update README.md
[fix] add 0.10 link, fixeshttp-party#459
Send path in req.path and not the url
Conflicts:
lib/node-http-proxy/http-proxy.js
I spent quite a lot of time trying to getting a websocket proxy working on 0.10 before digging through the issues and realising 0.10 isn't supported. Maybe it would be worth adding a note to the readme that node-http-proxy is only compatible with 0.8?
The text was updated successfully, but these errors were encountered: