Closed EthanLozano closed 3 years ago
👍
@0xTim - any progress with this review?
@lmcd currently trying to write a failing test for it. If I can't get one done by tomorrow I'll just merge
@0xTim I found the simplest way to reproduce the issue and commented on the issue's page. The issue is exposed when SSL is enabled. The current TLS test only has websocket-kit on the client-side, and I think you want a test where websocket-kit's source code is used on both the server and the client? idk.
Resolves an issue where web socket connections weren't being closed after being sent a
close()
from the client on TLS connections (#89). Resolves (#86)