Re: TCP & curl-loader question

[Robert I. <cor...@gm...>]

hi Gary

On Sat, Nov 1, 2008 at 6:57 PM, Gary Fitts <ga...@in...> wrote:

> I did use the URL facility, and the same thing happens. I don't have
> that conf and log file around anymore. I can reconstruct them if you'd
> like to see them.
>

I have filtered the problematic TCP session from your capture by the filter
below in wireshark:

(ip.addr eq 65.105.205.215 and ip.addr eq 65.105.205.203) and (tcp.port eq
38507 and tcp.port eq 9000)


Client initiates closure: 38507 > cslistiner FIN-ACK Seq=5013
Server responds by ACK to that packet - ACK Ack=5014 (5014=5013+1)

Now server is expected to send FIN-ACK, but what it does is as he has a
SO_LINGER
option at his socket:
a) send the last data packet
b) afterwards sends FIN-ACK

So far so good, but client does not like (and this is also legal), that
server sends him
data packets after the FIN-ACK acknowledged by ACK and sends RST.

I would say, that nothing serious besides that the TCP-stacks of the server
and client
are tuned a bit different.

Is it a server with a Microsoft operating system?
-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
Assistive technology that understands you
......................................................................