[squid-dev] is this really an ICAP 206 response "protocol error", if so what?

[Eliezer Croitoru]

I have tried to do something that horrified me for a very long time 
"looking at a ALL,9 debug!".

What I have found is an exception in the logs which results in 
"ICAP_ERR_OTHER" but I am unable to understand what the issue is.

The lines from the log are:
2015/11/13 01:47:22.072 kid1| 0,3| TextException.cc(87) Throw: 
ModXact.cc:918: exception: state.allowedPostview206
2015/11/13 01:47:22.072 kid1| 93,3| 
../../../src/base/AsyncJobCalls.h(177) dial: 
Adaptation::Icap::Xaction::noteCommRead threw exception: 
state.allowedPostview206
2015/11/13 01:47:22.072 kid1| 45,9| cbdata.cc(492) cbdataReferenceValid: 
0x8640ea8
2015/11/13 01:47:22.072 kid1| 11,5| HttpRequest.cc(474) detailError: 
current error details: 35/396407110
2015/11/13 01:47:22.072 kid1| 93,4| Xaction.cc(514) setOutcome: 
ICAP_ERR_OTHER
2015/11/13 01:47:22.072 kid1| 93,4| ServiceRep.cc(80) noteFailure: 
failure 1 out of 10 allowed in 0sec [up,fail1]


And the full cache.log is at:
http://ngtech.co.il/squid/icap_206_error/cache_debug_all_9.log
or compressed at:
http://ngtech.co.il/squid/icap_206_error/cache_debug_all_9.tar.gz

I am unsure what caused the issue from squid point of view.

Thanks,
Eliezer

On 13/11/2015 01:38, Alex Rousskov wrote:
> On 11/12/2015 04:09 PM, Eliezer Croitoru wrote:
>> I have been experimenting with ICAP and 206 response.
> ...
>
>> I have couple special cases which result in a "protocol error" but
>> nothing more then that.
>
> Since you can reproduce this error, you should be able to tell where
> Squid detects a "protocol error". Knowing that place may help you (or
> others) fix Squid, 206 specs, and/or your ICAP service.
>
>
>> I have attached two wireshark dumps which one works while the other
>> result in a protocol error.
>
> FWIW, I do not see anything obviously wrong in those dumps.
>
>
> Cheers,
>
> Alex.
>