Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emit disconnected event instead of error when ECONNRESET #966

Merged
merged 2 commits into from
Jun 3, 2016

Commits on Feb 24, 2016

  1. Emit disconnected event instead of error when ECONNRESET

    ECONNRESET means the other side of the TCP conversation abruptly
    closed its end of the connection.
    
    If we get an ECONNRESET error from the proxy request and the
    socket is destroyed this means that the client has closed
    his connection, and emit this as an error can lead to
    confusion and hacks to filter that kind of message.
    
    I think that the best we can do is abort and emit another event,
    so if any caller wants to handle with that kind of error, he can
    by listen the disconnected event.
    
    http-party#813
    Deividy committed Feb 24, 2016
    Configuration menu
    Copy the full SHA
    7d68d02 View commit details
    Browse the repository at this point in the history

Commits on Feb 25, 2016

  1. Configuration menu
    Copy the full SHA
    bfcad94 View commit details
    Browse the repository at this point in the history