Re: [squid-users] GET/PUT Question - AGAIN

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Tue, 5 Oct 2004 18:15:28 +0200 (CEST)

What does the requests you send to Squid look like?

ngrep is a generally better tool for looking at the HTTP protcol details.

Regards
Henrik

On Mon, 4 Oct 2004, OTR Comm wrote:

> Hello,
>
> I managed to get squid to accept a single file that I can push to it
> from a MS Windows application that I am developing.
>
> Now I am trying to send two during the same session. But I am having
> problems.
>
> BTW: squid is listening on 216.19.43.110:3128, and my Windows platform
> is pushing from 192.168.1.254
>
> When I push the first file, squid comes back with 'HTTP/1.0 200 OK'
>
> Using snort to monitor port 3128, I get:
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> 10/04-19:06:13.740922 216.19.43.110:3128 -> 192.168.1.254:2160
> TCP TTL:64 TOS:0x0 ID:34359 IpLen:20 DgmLen:40 DF
> ***A**** Seq: 0x40A75EE0 Ack: 0x7701A35C Win: 0x2DA0 TcpLen: 20
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> 10/04-19:06:13.744075 216.19.43.110:3128 -> 192.168.1.254:2160
> TCP TTL:64 TOS:0x0 ID:34360 IpLen:20 DgmLen:58 DF
> ***AP*** Seq: 0x40A75EE0 Ack: 0x7701A35C Win: 0x2DA0 TcpLen: 20
> 48 54 54 50 2F 31 2E 30 20 32 30 30 20 4F 4B 0D HTTP/1.0 200 OK.
> 0A 00 ..
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> 10/04-19:06:13.744403 216.19.43.110:3128 -> 192.168.1.254:2160
> TCP TTL:64 TOS:0x0 ID:34361 IpLen:20 DgmLen:40 DF
> ***A***F Seq: 0x40A75EF2 Ack: 0x7701A35C Win: 0x2DA0 TcpLen: 20
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> 10/04-19:06:13.744573 192.168.1.254:2160 -> 216.19.43.110:3128
> TCP TTL:128 TOS:0x0 ID:60795 IpLen:20 DgmLen:40 DF
> ***A**** Seq: 0x7701A35C Ack: 0x40A75EF3 Win: 0xFADE TcpLen: 20
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> afer squid recives and caches the first file. Then when I send the
> second file, I see it go past in snort, but squid doesn't acknowledge
> that it came in. No errors, nothing shows up as I am tailing on the
> cache.log (with custom debugging hooks), and nothing shows up in
> store.log or access.log. The file sizes are correct, and the 'PUT'
> header contains the correct Content-Length for the second file, but it
> will not cache.
>
> What I see in snort after the second file transfers is a response back
> from squid:
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> 10/04-19:06:22.789730 216.19.43.110:3128 -> 192.168.1.254:2160
> TCP TTL:64 TOS:0x0 ID:0 IpLen:20 DgmLen:40 DF
> *****R** Seq: 0x40A75EF3 Ack: 0x0 Win: 0x0 TcpLen: 20
>
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
>
> I don't know why squid is sending back ID:0, Ack:0x0, and Win:0x0
>
> Am I missing something that my PUSH client is suppose to send squid to
> tell it to get ready for another file?
>
> Thanks,
> Murrah Boswell
>
Received on Tue Oct 05 2004 - 10:15:30 MDT

This archive was generated by hypermail pre-2.1.9 : Mon Nov 01 2004 - 12:00:01 MST