On 2023-09-03 09:39, Ben Goz wrote:
I'm working with squid that sends http/s traffic to a custom c-icap filter. I see a lot of ICAP reply debug messages in Squid's cache log. kid1| 93,3| ModXact.cc(556) readMore: not reading because ICAP reply pipe is full What are the implications of this message?
It implies several things, including that you are looking at debugging output meant for Squid developers, not Squid administrators (and this mailing list) :-).
How can I find out what is the root cause of this message?
A Squid developer would start by looking at the corresponding code (src/adaptation/icap/ModXact.cc line 556). You can ask here (like you are doing), but, IMO, you should not. I recommend focusing on (or starting with) the high-level problem you are trying to solve rather than a low-level debugging message.
Can I increase the ICAP reply pipe in Squid's configuration?
You cannot -- the pipe buffer will not grow beyond 64KB, a hard-coded limit (BodyPipe::MaxCapacity). However, bugs notwithstanding, the pipe may be full not because it is too small, but because the adapted HTTP message body consumer on the other side of this pipe (i.e. Squid, Squid client, origin server, or cache_peer) cannot consume ICAP response bytes fast enough.
HTH, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx https://lists.squid-cache.org/listinfo/squid-users
