aboutsummaryrefslogtreecommitdiffstats
path: root/erts/obj
diff options
context:
space:
mode:
authorRory Byrne <[email protected]>2015-04-20 10:57:53 +0100
committerRory Byrne <[email protected]>2015-06-09 20:50:06 +0100
commit4f63e427f1345b40b484ef16f6ff5e922bf14dac (patch)
treef7e1e7ddf8d24c2beacc09d67e6989cca431c61f /erts/obj
parentf1dede329de90e4805cd21a43bb5b19e288c81a3 (diff)
downloadotp-4f63e427f1345b40b484ef16f6ff5e922bf14dac.tar.gz
otp-4f63e427f1345b40b484ef16f6ff5e922bf14dac.tar.bz2
otp-4f63e427f1345b40b484ef16f6ff5e922bf14dac.zip
Add 'show_econnreset' TCP socket option
An ECONNRESET is a socket error which tells us that a TCP peer has sent an RST. The RST indicates that they have aborted the connection and that the payload we have received should not be considered complete. Up until now, the implementation of TCP in inet_drv.c has hidden the receipt of the RST from the user, treating it as though it was just a FIN terminating the read side of the socket. There are many cases where user code needs to be able to distinguish between a socket that was closed normally and one that was aborted. Setting the option {show_econnreset, true} enables the user to receive ECONNRESET errors on both active and passive sockets. A connected socket returned from gen_tcp:accept/1 will inherit the show_econnreset setting of the listening socket. By default this option is set to {show_econnreset, false}. Note that this patch only enables the reporting of ECONNRESET when the socket is being read from. It does not report ECONNRESET (or EPIPE) when the user tries to write to a connection when an RST has already been received. Currently the TCP implementation in inet_drv.c hides all such send errors from the user in favour of returning {error, close}. A separate patch will be needed to enable the reporting of such errors.
Diffstat (limited to 'erts/obj')
0 files changed, 0 insertions, 0 deletions