Hi all,

I am having problems getting squid to work with a bespoke ICAP server we have written.

Suse (SLED) 10 SP 2, Squid v3.3.0 Stable 1-1.2

I have Squid working as a proxy for the local lan, and configured to REQMOD to an ICAP server. The ICAP server is existing code, that has functioned correctly with Bluecoat.

The Squid server requests "OPTIONS" from teh ICAP server, the ICAP server replies with the "REQMOD" option, Squid then send a totally empty packet to teh socket the ICAP is listening on - the TCP packer has 0 bytes of payload - where as my understanding is that it should send headers and client IP

Squid Config:-

# define internal network and allow http access for this network
acl privatenet src 10.1.0.0/255.255.0.0
http_access allow privatenet

icap_enable on
icap_service WEBc reqmod_precache 0 icap://10.1.70.4:1344/reqmod
icap_send_client_ip on


icap_class WC WEBc
icap_access WC allow privatenet


icap_connect_timeout 70.00 seconds
icap_service_revival_delay 30


icap_persistent_connections on


# default is on
icap_preview_enable on
icap_preview_size 0


# for testing
icap_service_failure_limit 10

Our ICAP server provides us with the following log of inbound and outbound data:-

Data from SQUID:


OPTIONS icap://10.1.70.4:1344/reqmod ICAP/1.0
Host: 10.1.70.4:1344



Reply from ICAP server to SQUID:

ICAP/1.0 200 OK
Date: Wed, 24 Jun 2009 12:25:21 GMT
Methods: REQMOD
Service: WEBconsent ICAP Server
ISTag: "W3E4R7U9-L2E4-2"
Encapsulated: null-body=0
Max-Connections: 100
Options-TTL: 7200


After this, using a network monitor SQUID replies with an empty TCP data packet - no payload at all within the packet.

The usual retry etc then occurs with the same data

Any help gratefully received!!


tia
Dave