Aymeric Augustin comments

Results 368 comments of


                                            Aymeric Augustin

question: intended behavior with failed auth and async for auto-reconnect

Now available in version 13.1, which I just released.

Expose list of connections as an attribute of WebSocketServer

Follow-up task: update documentation to take advantage of this new API.

Expose list of connections as an attribute of WebSocketServer

Documentation was updated, notably in 61a6a7a99534e2522773476fc72ca615f5a6ea97 and 667e418ae474235c2bc26024df11c8e1d573d27a.

Threading server should close connections on exit

This would also be more elegant than f9cea9cca568dc92704de3744639eb4248278a8f.

Threading server should close connections on exit

Implementing this may hit #1596.

Respond with HTP 414 or 431 when exceeding security limits

Honestly it's not important and I'm not even sure the complexity is worth doing it at all. I made a note in case one day I want to relax by...

Race condition in sync implemention delays closing connections

This race condition affects the opening handshake only. Your tests are after the opening handshake so they don't reproduce it. Also, it's a race condition, meaning that it doesn't happen...

Unable to suppress traceback when opening handshake fails

Does of of these option work for you? https://websockets.readthedocs.io/en/stable/topics/logging.html#disable-logging

Unable to suppress traceback when opening handshake fails

Probably you want: `logging.getLogger("websockets").setLevel(logging.CRITICAL)`

Unable to suppress traceback when opening handshake fails

Closing the issue for now — but feel free to comment if my answers above don't really solve your problem.