Alex Villacís Lasso d4c9bcdd37 Prevent spurious RX timeout/close on incoming socket object ...

When accepting a socket from an incoming connection, the internal fd was
assigned without updating the field for last RX activity. If the remote
side did *not* immediately write to the connection, or otherwise the
socket could not be internally checked for incoming data, AND the
higher-level code set up a RX timeout value, the 125-ms interval polling
might evaluate the socket RX timeout condition with a last RX activity
timestamp of zero (as per the default constructor). This caused a
spurious RX timeout and incorrect socket closing. Fixed by initializing
the field when the new incoming connection socket is accepted.

2022-09-02 17:52:50 -05:00

examples

Update/fix SSL example sketch to include required build_opt.h

2022-01-17 11:26:49 -05:00

src

Prevent spurious RX timeout/close on incoming socket object

2022-09-02 17:52:50 -05:00

library.json

Arduino library files

2020-12-21 12:59:04 -05:00

library.properties

Arduino library files

2020-12-21 12:59:04 -05:00

LICENSE

Place code under the same license as original AsyncTCP

2020-12-21 13:16:21 -05:00

Description

No description provided

95 KiB

Languages

C++ 100%