TCP reset caused by socket.py

[Bjoern Schliessmann]

Object01 wrote:
> The server is multithreaded, handling each request on its own
> thread.

Ugh.

> But is a RST really a part of a valid close operation?  

Depends on the state of the parties :) The proper way to close
non-defunct connections is using FIN segments.

> It was my understanding that the RST is used to indicate a problem
> with the connection, usually a half-open connection.  I never see
> RSTs unless this error occurs.

RFC793:

| Reset Generation
|
| As a general rule, reset (RST) must be sent whenever a segment
| arrives which apparently is not intended for the current
| connection.  A reset must not be sent if it is not clear that this
| is the case. 

Regards,


Björn

-- 
BOFH excuse #347:

The rubber band broke