[lwip-devel] [bugs #9455] The sockets API does not correctly inform a process that a RST has been received

[Kieran Mansley]

This mail is an automated notification from the bugs tracker
 of the project: lwIP - A Lightweight TCP/IP stack.




/**************************************************************************/
[bugs #9455] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9455>
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: Kieran Mansley
On: Fri 06/25/04 at 14:28

Category:  sockets
Severity:  5 - Average
Item Group:  Faulty Behaviour
Resolution:  None
Assigned to:  None
Status:  Open


Summary:  The sockets API does not correctly inform a process that a RST has 
been received

Original Submission:  If a process is only using send()/write() etc rather than 
any recv()/read() calls, it will not learn that a connection has been closed 
and a FIN/RST received.

The receipt of a RST by the sending process indicates that
the remote process has terminated.

When a process writes to a socket that has received a RST, the SIGPIPE
signal should be sent to the process.  The default action of this signal
is to terminate the process.  If the process either catches the signal
and returns from the signal handler, or ignores the signal, the write
operation returns EPIPE.











For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9455>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/