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 Apr 22, 2023. It is now read-only.
This change was unintended, but I am not sure whether we want to fix it. I mean, when you specify both a host and a pipe name, you're almost asking for undefined behaviour. Does this cause you a lot of trouble?
E.g., I am using http-proxy. Without modification, this module will not work over named pipes on 0.8.0. I've already made changes in my version of http-proxy to comply with new 0.8.0 interface and I will send pull request to http-proxy owners if node's interface is not going to change.
I guess, this change in 0.8.0 will cause issues with other modules, so it is a question of fixing all usages or creating backward compatibility fallback in node. Both approaches make sense.
Worked well with 0.6.*
See simple script that demonstrates: https://gist.github.com/3003574
On 0.6.19 the output:
on 0.8.0 the output:
The text was updated successfully, but these errors were encountered: