On 8/28/21 17:10, Alex Rousskov wrote:
Sorry for taking so long.
Meanwhile I upgraded to Squid 5.0.6, but the problem was not solved.
Reproduce the problem using a single transaction on an otherwise idle
Squid with full debugging enabled and share the corresponding cache.log:
https://wiki.squid-cache.org/SquidFaq/BugReporting#Debugging_a_single_transaction
It's here:
https://www.netfence.it/download/cache.log.bz2
Or, is there any way I can tell Squid to avoid passing FTP traffic
(coming on port 2121) to ICAP (while of course doing that for the rest)?
Yes, the adaptation_access directive controls what traffic goes to your
ICAP services. To match ftp_port traffic, I would give the ftp_port a
name and then try using that name in a myportname ACL. Other ACLs may
also work, but I would start with myportname. If myportname does not
work for ftp_port traffic, it is a Squid bug.
This works.
Thanks!
bye
av.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
