On 2024-03-18 18:46, Arun Kumar wrote:
Any idea, the reason for error in ModXact.cc parsePart fuction.
Happening during parsing the response from ICAP
parsePart: have 144 head bytes to parse; state: 0
parsePart: head parsing result: 0 detail: 600
AFAICT, Squid considers received ICAP response header malformed. More
than five possible problems/cases may match the above lines. The answer
to your question (or an additional clue!) is in different debugging
output, possibly logged somewhere between the two lines quoted above.
The right debugging lines may be visible in "debug_options ALL,2 58,5,
93,5" output, but it is usually best to share compressed ALL,9 logs
(privately if needed).
https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction
Sharing the problematic ICAP response (header) in a raw packet capture
format (to preserve important details) may also be very useful.
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
