Re: squid 3.1 ICAP problem

From: Henrik Nordstrom <henrik_at_henriknordstrom.net>
Date: Sun, 25 Apr 2010 22:22:55 +0200

fre 2010-04-23 klockan 16:43 +0100 skrev Dan Searle:
> 16:36:29.552442 IP localhost.1344 > localhost.50566: P 1:195(194) ack 72
> win 512 <nop,nop,timestamp 62423291 62423291>
> 0x0000: 4500 00f6 7ac7 4000 4006 c138 7f00 0001 E...z.@.@..8....
> 0x0010: 7f00 0001 0540 c586 bdca fa3d bd99 b529 .....@.....=...)
> 0x0020: 8018 0200 feea 0000 0101 080a 03b8 80fb ................
> 0x0030: 03b8 80fb 3230 3020 4f4b 0d0a 4461 7465 ....200.OK..Date

THat's not a correct ICAP response status line.. Should be

        ICAP/1.0 200 OK

Just as for HTTP ICAP responses always start with the ICAP protocol
identifier & version.

RFC3507 4.3.3 Response Headers, first paragraph.

Regards
Henrik
Received on Sun Apr 25 2010 - 20:19:31 MDT

This archive was generated by hypermail 2.2.0 : Mon Apr 26 2010 - 12:00:13 MDT