Re: clarification of CD termination code

2010-08-04 Thread Willy Tarreau
On Wed, Aug 04, 2010 at 04:29:08PM -0700, Bryan Talbot wrote: > In the tcpdump listed below, isn't the next-to-the-last RST also include an > ACK of the data previously sent? If that is the case, then the client has > received all of the data and ACK'd it but then rudely closed the TCP > connectio

Re: clarification of CD termination code

2010-08-04 Thread Jeffrey 'jf' Lim
On Thu, Aug 5, 2010 at 7:29 AM, Bryan Talbot wrote: > In the tcpdump listed below, isn't the next-to-the-last RST also include an > ACK of the data previously sent?  If that is the case, then the client has > received all of the data and ACK'd it but then rudely closed the TCP > connection without

Re: clarification of CD termination code

2010-08-04 Thread Bryan Talbot
In the tcpdump listed below, isn't the next-to-the-last RST also include an ACK of the data previously sent? If that is the case, then the client has received all of the data and ACK'd it but then rudely closed the TCP connection without the normal FIN exchange. Is my reading correct? 19:03:33.

Re: clarification of CD termination code

2010-08-02 Thread Willy Tarreau
On Wed, Jul 28, 2010 at 05:51:18PM -0700, Bryan Talbot wrote: > I'm trying to figure out what _exactly_ the CD termination code means. The > docs says: > > CD The client unexpectedly aborted during data transfer. This can be > caused by a browser crash, by an intermediate equipme