<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"><head><!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><body><div class="ydpe59eedc4yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">I managed to reproduce the problem in my personal setup. Please find the cache logs when the problem is reproduced. Squid version is 5.8</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><a href="https://drive.google.com/file/d/19yirXfxKli7NXon4ewiy-v3GpLvECT1i/view?usp=sharing" rel="nofollow" target="_blank" class="enhancr_card_4364899239">cache.zip</a><br></div><div><br></div><div id="ydp8c7d8e13enhancr_card_4364899239" class="ydp8c7d8e13yahoo-link-enhancr-card ydp8c7d8e13ymail-preserve-class ydp8c7d8e13ymail-preserve-style" style="max-width:288px;font-family:YahooSans VF, YahooSans, OpenSans VF, Helvetica Neue, Segoe UI, Helvetica, Arial, sans-serif;display:inline-block" data-url="https://drive.google.com/file/d/19yirXfxKli7NXon4ewiy-v3GpLvECT1i/view?usp=sharing" data-type="YENHANCER" data-size="MINI" contenteditable="false"><a href="https://drive.google.com/file/d/19yirXfxKli7NXon4ewiy-v3GpLvECT1i/view?usp=sharing" style="text-decoration:none !important;color:#000 !important" class="ydp8c7d8e13yahoo-enhancr-cardlink" rel="nofollow" target="_blank"><table border="0" class="ydp8c7d8e13card ydp8c7d8e13yahoo-ignore-table" cellpadding="0" cellspacing="0" width="288" height="80" style="border-width:1px;border-style:solid;border-color:rgb(224, 228, 233);width:288px;background-color:#fff;border-radius:2px"><tbody><tr><td width="10px" style="width:10px"></td><td><img class="ydp8c7d8e13card-object" src="https://s.yimg.com/lb/brands/80x80_google.png" width="24" height="24" data-inlineimagemanipulating="true"><h2 class="ydp8c7d8e13card-title" style="font-size: 14px; line-height: 16px; color: rgb(29, 34, 40); font-family: YahooSans VF, YahooSans, OpenSans VF, Helvetica Neue, Segoe UI, Helvetica, Arial, sans-serif; margin: 4px 0px; max-width: 186px; text-decoration: none !important;">cache.zip</h2></td></tr></tbody></table></a></div><div><br></div><div><br></div><div><br></div>
</div><div id="ydp83d55996yahoo_quoted_4923519064" class="ydp83d55996yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, March 22, 2024 at 11:02:51 PM EDT, Alex Rousskov <rousskov@measurement-factory.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On 2024-03-22 13:11, Arun Kumar wrote:<br clear="none">> The lines above are. The content-length is 138 (8a in hex), but the <br clear="none">> bytes are 144. Could this be the reason?<br clear="none">> <br clear="none">> parseMore: have 144 bytes to parse [FD 14;RBG/Comm(14)wr job24]<br clear="none">> parseMore:<br clear="none">> 8a^M<br clear="none">> {"activity":"Make a simple musical <br clear="none">> instrument","type":"music","participants":1,"price:0.4,"link":"","key":"7091374","accessibility":0.25}^M<br clear="none">> parseHeaders: parse ICAP headers<br clear="none">> parsePart: have 144 head bytes to parse; state: 0<br clear="none">> parsePart: head parsing result: 0 detail: 600<br clear="none"><br clear="none"><br clear="none">I cannot be sure based on the tiny snippets shared so far, but it <br clear="none">_looks_ like Squid expected an ICAP response header and got an ICAP <br clear="none">response body chunk instead. It is also possible that we are looking at <br clear="none">log lines from two unrelated ICAP transactions, or I am simply <br clear="none">misinterpreting the snippets.<br clear="none"><br clear="none">If you want a more reliable diagnosis, then my earlier recommendation <br clear="none">regarding sharing (privately if needed) the following information still <br clear="none">stands:<br clear="none"><br clear="none">* compressed ALL,9 cache.log and<br clear="none">* the problematic ICAP response in a raw packet capture format.<br clear="none"><br clear="none"><br clear="none">HTH,<br clear="none"><br clear="none">Alex.<div class="ydp83d55996yqt1772414351" id="ydp83d55996yqtfd92492"><br clear="none"><br clear="none"><br clear="none">> On Monday, March 18, 2024 at 11:21:02 PM EDT, Alex Rousskov <br clear="none">> <<a shape="rect" href="mailto:rousskov@measurement-factory.com" rel="nofollow" target="_blank">rousskov@measurement-factory.com</a>> wrote:<br clear="none">> <br clear="none">> <br clear="none">> On 2024-03-18 18:46, Arun Kumar wrote:<br clear="none">> <br clear="none">> > Any idea, the reason for error in ModXact.cc parsePart fuction.<br clear="none">> > Happening during parsing the response from ICAP<br clear="none">> ><br clear="none">> ><br clear="none">> > parsePart: have 144 head bytes to parse; state: 0<br clear="none">> > parsePart: head parsing result: 0 detail: 600<br clear="none">> <br clear="none">> <br clear="none">> AFAICT, Squid considers received ICAP response header malformed. More<br clear="none">> than five possible problems/cases may match the above lines. The answer<br clear="none">> to your question (or an additional clue!) is in different debugging<br clear="none">> output, possibly logged somewhere between the two lines quoted above.<br clear="none">> The right debugging lines may be visible in "debug_options ALL,2 58,5,<br clear="none">> 93,5" output, but it is usually best to share compressed ALL,9 logs<br clear="none">> (privately if needed).<br clear="none">> <br clear="none">> <a shape="rect" href="https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction" rel="nofollow" target="_blank">https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction</a> <<a shape="rect" href="https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction" rel="nofollow" target="_blank">https://wiki.squid-cache.org/SquidFaq/BugReporting#debugging-a-single-transaction</a>><br clear="none">> <br clear="none">> <br clear="none">> Sharing the problematic ICAP response (header) in a raw packet capture<br clear="none">> format (to preserve important details) may also be very useful.<br clear="none">> <br clear="none">> <br clear="none">> HTH,<br clear="none">> <br clear="none">> Alex.<br clear="none">> <br clear="none">> <br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>