Hello,
Following is an Ethereal dump of an HTTP request for a graphic. The browser
requesting the file is IE 6.01, but I have seen this on Netscape also.
In line 4, "C HTTP GET /titleMIH.gif HTTP/1.1" was corrupted at reception
and did not pass the checksum routine (ok, fine). Next the connection
closes.
Curiously, the client asks for the file again, without ever setting up the
connection (so it seems to me). The server then ACKS, I think (8), and then
the conversation ends.
Could someone offer me an explanation as to what might be happening here
and if there is any necessary tweaking that might go on in the server code
to recover? Is this conversation proper in light of the fact the the second
request may have been dropped at the hardware also? Any comments to the
appropriateness of how the browser is acting in this conversation is
certainly
welcome.
Thanks,
Tom Barker
1 C TCP 2394 > http [SYN] Seq=1716877397 Ack=0 Win=65535 Len=0
2 S TCP http > 2394 [SYN, ACK] Seq=9296 Ack=1716877398 Win=2048 Len=0
3 C TCP 2394 > http [ACK] Seq=1716877398 Ack=9297 Win=65535 Len=0
4 C HTTP GET /titleMIH.gif HTTP/1.1
5 S TCP http > 2394 [FIN, ACK] Seq=9297 Ack=1716877398 Win=2048 Len=0
6 C TCP 2394 > http [ACK] Seq=1716877667 Ack=9298 Win=65535 Len=0
7 C TCP 2394 > http [FIN, ACK] Seq=1716877667 Ack=9298 Win=65535 Len=0
8 S TCP http > 2394 [ACK] Seq=9298 Ack=1716877398 Win=2048 Len=0
9 C HTTP GET /titleMIH.gif HTTP/1.1
10 S TCP http > 2394 [ACK] Seq=9298 Ack=1716877667 Win=2048 Len=0
11 C TCP 2394 > http [FIN, ACK] Seq=1716877667 Ack=9298 Win=65535 Len=0
12 S TCP http > 2394 [RST, ACK] Seq=9299 Ack=1716877668 Win=2048 Len=0