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
setTimeout in Node 9+ no longer works if the socket is not yet connected. This breaks at least the test suite of Proxilate and also behaviour. Setting the socket timeout option isn't yet working (I believe) due to limitations in http-proxy.
Worth keeping an eye on any workarounds/fixes in http-proxy as it will need to be updated here. There are also numerous out of date dependencies worth taking a look at.
The text was updated successfully, but these errors were encountered:
Probably related to this: http-party/node-http-proxy#1455
setTimeout
in Node 9+ no longer works if the socket is not yet connected. This breaks at least the test suite of Proxilate and also behaviour. Setting the socket timeout option isn't yet working (I believe) due to limitations in http-proxy.Worth keeping an eye on any workarounds/fixes in http-proxy as it will need to be updated here. There are also numerous out of date dependencies worth taking a look at.
The text was updated successfully, but these errors were encountered: