Re: [squid-users] Getting connection port with ICAP or eCAP

Hi,

I Don't understand how do to combine an ICAP url ( like "icap_service
qlproxy1 reqmod_precache bypass=0 icap://127.0.0.1:1344/reqmod" ) with
an ACL to use it only for traffic who reaches squid at a specific
port. (one of the ports squid listens on ) can you please help me
with an example?

Much appreciated!

--------- Forwarded message ----------
From: Eliezer Croitoru <eliezer_at_ngtech.co.il>
To: squid-users_at_squid-cache.org
Cc:
Date: Tue, 06 Nov 2012 17:20:58 +0200
Subject: Re: [squid-users] Getting connection port with ICAP or eCAP
On 11/6/2012 5:09 PM, Sharon Sahar wrote:
Hi,

I understood that when using ICAP or eCAP, you basically receive the
response and request body and headers, and there is an option to
direct squid to send the client ip as well.

I wonder, is there a way to instruct squid to send the listening port
on which this client connection was received? (we use different
listening ports to differentiate between users)
Received on Wed Nov 14 2012 - 08:17:26 MST