Problem with TCP RST (reset) packets about easywsclient HOT 2 OPEN

Thanks for reporting this. Which side is initiating the close? When initiating close from easywsclient, it will do this:

1. It will queue a opcode=close (0x8) message for transmission in txbuf.
2. On the subsequent calls to pull(), easywsclient will try to flush out the tx queue (txbuf).
3. Finally, call close() on the socket when txbuf is empty (which should send RST from easywsclient).

Question for you: after step 3, what ACK packet is there to be handled? Let me know if I misunderstood this. Thanks.

from easywsclient.

So, after the pull() the other side sends an ACK and then easywsclient sends a RST. I'm guessing the RST is actually sent my the kernel as easywsclient has closed the socket already. I'm not sure if this ACK is handled or not to be honest and I'm not sure how to test it.

from easywsclient.