Skip to content

Connection errors are not exposed #374

@pimterry

Description

@pimterry

connection.on('error', function () {
socket.destroy()
})

Here ⬆️ the server listens for connection errors, and then silently shuts down the socket.

It doesn't provide any easy way to listen for these errors though, like Node HTTP/1.1's clientError event or HTTP/2's sessionError event, so code using node-spdy never knows that this has happened.

This can be useful for error reporting and monitoring. I'm going to work around this manually in my application, but built-in support would be useful. Are you be open to a PR adding this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions