closing server econnrefused

[yawnt]

https://github.com/yawnt/caronte/issues/10

[yawnt]

this should be fixed since error handling is now implemented.. @jcrugzz feel free to reopen if it's not the case

[jcrugzz]

The following example results in...

/n/j/proxy ❯❯❯ node primus-proxy.js
{ from: 'client', to: 'server' }
disconnected
{ from: 'server', to: 'client' }

/Users/jcrugzz/node.js/nodejitsu/node-http-proxy/lib/caronte/passes/web-incoming.js:108
        throw err;
              ^
Error: connect ECONNREFUSED
    at errnoException (net.js:901:11)
    at Object.afterConnect [as oncomplete] (net.js:892:19)

For one the error should be handled if the EventEmitter2 wildcards are working properly so I have not yet determined if the client will receive the end event (which it should) upon the server being destroyed due to the proxy crashing the process.

cc @yawnt

[jcrugzz]

@cronopio also we should have tests for cases like this for all the various transports as I believe we will hit some edge cases with various disconnects being triggered.

[cronopio]

Ok, @jcrugzz by now there are tests for ws and socket.io and not for primus, I'll try to write it

[jcrugzz]

@cronopio thanks! and make sure the test cases handle when the server closes and the proxy errors. Keep up the good work :)