[squid-users] Slow read for ICAP REQMOD body
dsmith at travelrepublic.co.uk
Mon Nov 16 15:13:22 UTC 2015
I'd much rather not write my own but for *reasons* I need an implementation that runs on .NET and I couldn't find one.
I only need a pretty small subset of the protocol.
Both those bugs are for squid >= 3.5. I'm on 3.3.8
Perhaps I should try a more recent version.
From: Alex Rousskov [mailto:rousskov at measurement-factory.com]
Sent: 16 November 2015 15:07
To: squid-users at lists.squid-cache.org
Cc: David Smith
Subject: Re: [squid-users] Slow read for ICAP REQMOD body
On 11/16/2015 07:30 AM, David Smith wrote:
> I’m in the middle of writing an ICAP server.
If you are not too far along down this path, consider writing an adapter for one of the existing ICAP servers and/or eCAP. ICAP is far more complex than it seems, and, in most cases, reinventing that [complex] wheel is a bad idea. I am a biased ICAP server seller, and your YMMV, but I have seen too many folks suffer through such projects to resist commenting.
> Reading the encapsulated body of a REQMOD message from Squid is taking
> 300ms. Reading the ICAP headers / HTTP headers is extremely quick.
Could it be Squid bug 4353?
More information about the squid-users