[squid-users] Squid 3.5 ICAP Problems
Amos Jeffries
squid3 at treenet.co.nz
Fri Nov 3 15:17:46 UTC 2017
You seem to be mixing up terminology and software names quite a bit and
its making your post quite confusing even for those of us who know the
subject matter.
"C-ICAP" is the name of a piece of server software. There is no "C-ICAP
module in Squid".
ICAP is a networking protocol. Both C-ICAP and Squid software support
and use the ICAP protocol to exchange messages between each other.
AFAIK, there are no queues in Squid ICAP handling. Messages are
delivered sequentially on ICAP connections with the response waited for
before the next is sent. There _are_ multiple persistent connections
running in parallel, but should not be message pipelining.
The UP/DOWN messages in cache.log occur when the ICAP protocol server
(C-ICAP software) stops responding to the small OPTIONS messages.
Amos
More information about the squid-users
mailing list