Skip to content

ws.on :close not always triggered #24

Open
@rubys

Description

@rubys

I've found two cases where ws.on :close is not triggered, both involving the server going down. First is with a em-websocket server, and the second is with a secure: true connection with a WebSocket-EventMachine-Server server.

A possible fix is to replace sleep 1 with close in client.rb.

To reproduce, use the websocket-client-simple example with either the em-websocket example or with the WebSocket-EventMachine-Server example modified for TLS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions