Results 1 to 1 of 1
Thread: Squid icap reqmod
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Jun 2009
Squid icap reqmod
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
# 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_service WEBc reqmod_precache 0 icap://10.1.70.4:1344/reqmod
icap_class WC WEBc
icap_access WC allow privatenet
icap_connect_timeout 70.00 seconds
# default is on
# for testing
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
Reply from ICAP server to SQUID:
ICAP/1.0 200 OK
Date: Wed, 24 Jun 2009 12:25:21 GMT
Service: WEBconsent ICAP Server
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!!