On 26/10/2015 11:32 p.m., Vadim Rogoziansky wrote: > Hello All. > > I have a question about the size of ICAP request chunks. What is it and > is there a way to make it configurable? It is the size of data ready to be written on the socket when a write is scheduled. For the full details on the chunked transfer encoding see <http://tools.ietf.org/html/rfc7230#section-4.1> No it is not configurable. It depends on the proxy I/O speed. If Squid is doing little else but shuffling packets around the chunks get smaller, if CPU is taken up with other processing enough that data accumulates in the buffers then the chunks get bigger. > > I've made an investigation here and looks like Squid 3.5.9 separates the > ICAP payload on little chunks with the size of 27 bytes. This is probably a side effect of the bug 4353 / 4206 issue on the main I/O socket from the client. On a fast Squid the small input blobs being read in would stay small though all the rest of Squid operations, including the chunk sizes written to ICAP. See if the workaround patch in the bug report helps: <http://bugs.squid-cache.org/show_bug.cgi?id=4353> Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
