Squid 3.5.25 does not seem to recognise the 408 request timeout error code from ICAP.
The more troublesome issue for me is the exception it generates and then declares ICAP down after a certain number of such exceptions.
I don't want to disable the failure limit entirely given that we can often have genuine failures that squid needs to detect.
What i'd like to see is squid should not throw an exception in this case. The timeout is somewhat aggressive but works with an earlier version of ICAP (0.1.x). The one i'm testing is 0.5.3.
Any suggestions? I tried looking at squid 3.5.26 through 3.5.28 but i don't see any support for 408 timeout there (maybe i missed it?).
Debug Logs:
2018/10/29 20:20:25.656| 93,5| ModXact.cc(654) parseMore:
ICAP/1.0 408 Request timeout^M
Server: C-ICAP/0.5.3^M
Connection: close^M
ISTag: CI0001-XXXXXXXXX^M
^M
2018/10/29 20:20:25.656| 93,5| ModXact.cc(749) parseHeaders: parse ICAP headers
2018/10/29 20:20:25.656| 93,5| ModXact.cc(1079) parseHead: have 98 head bytes to parse; state: 0
2018/10/29 20:20:25.656| 93,5| ModXact.cc(1094) parseHead: parse success, consume 98 bytes, return true
2018/10/29 20:20:25.656| 93,5| ModXact.cc(785) parseIcapHead: found connection close
2018/10/29 20:20:25.656| 93,5| ModXact.cc(815) parseIcapHead: ICAP status 408
2018/10/29 20:20:25.656| 93,3| ../../../src/base/AsyncJobCalls.h(177) dial: Adaptation::Icap::Xaction::noteCommRead threw exception: Unsupported ICAP status code
2018/10/29 20:20:25.656| 11,5| HttpRequest.cc(472) detailError: current error details: 35/396407234
2018/10/29 20:20:25.656| 93,4| Xaction.cc(514) setOutcome: ICAP_ERR_OTHER
2018/10/29 20:20:25.656| 93,4| ServiceRep.cc(80) noteFailure: failure 4 out of 10 allowed in 0sec [up,fail4]
...
2018/10/29 20:21:06.981| 93,5| ModXact.cc(815) parseIcapHead: ICAP status 408
2018/10/29 20:21:06.981| 93,3| ../../../src/base/AsyncJobCalls.h(177) dial: Adaptation::Icap::Xaction::noteCommRead threw exception: Unsupported ICAP status code
2018/10/29 20:21:06.981| 11,5| HttpRequest.cc(472) detailError: current error details: 35/396407234
2018/10/29 20:21:06.981| 93,4| Xaction.cc(514) setOutcome: ICAP_ERR_OTHER
2018/10/29 20:21:06.981| 93,4| ServiceRep.cc(80) noteFailure: failure 11 out of 10 allowed in 0sec [up,fail11]
2018/10/29 20:21:06.981| suspending ICAP service for too many failures
regards,
Arun
Arun
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
