[squid-users] Transfer-Encoding tag not delivered to c-icap server
giray_simsek at hotmail.com
Tue Dec 15 13:11:17 UTC 2015
That was helpful. I looked at the ICAP request/response headers as well as the squid log.
After seeing the following line in the log file:
2015/12/15 11:52:58.104 kid1| 93,3| Xaction.cc(512) setOutcome: Warning: reseting outcome: from ICAP_MOD to ICAP_ERR_OTHER
I thought it must be caused by something on the icap side. And I verified that download problem occurs only for files larger than 5 MB.
Then I noticed that the icap av service's MaxObjectSize has a default value of 5MB.
Upping this number in the conf file solved my issue.
Thanks a lot.
> Subject: Re: [squid-users] Transfer-Encoding tag not delivered to c-icap server
> To: squid-users at lists.squid-cache.org
> CC: giray_simsek at hotmail.com
> From: rousskov at measurement-factory.com
> Date: Mon, 14 Dec 2015 10:02:24 -0700
> On 12/14/2015 08:33 AM, Giray Simsek wrote:
>> I am using squid + c-icap for content adaptation.
>> On a client machine, I am trying to download a pdf file from docs.google.com. Looks like the google servers are sending the response as chunked as the http headers look like below:
>> I listened to the packets that are delivered to icap server from
>> squid and verified that "Transfer-Encoding" header is not delivered
>> to icap server.
> This is normal. Squid decodes chunked transfer encoding before sending
> the message to the ICAP (or eCAP) service, as it should.
>> So I can't find out at what point the file download is being blocked.
>> File is downloaded successfully when the icap server is stopped. But
>> I guess the problem might be about squid's way of passing the file
>> content (or headers) to icap server. Is there anything I can do on
>> the icap server side to make the download succeed?
> You may want start by finding the ICAP request and response headers and
> posting them here. IIRC, Squid reports them with debug_options ALL,2
More information about the squid-users