<html><head></head><body><div class="ydp9ce37575yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false"><div><div dir="ltr" data-setdir="false">The lines above are. The content-length is 138 (8a in hex), but the bytes are 144. Could this be the reason?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">parseMore: have 144 bytes to parse [FD 14;RBG/Comm(14)wr job24]</div><div dir="ltr" data-setdir="false">parseMore:<br></div><div dir="ltr" data-setdir="false">8a^M</div><div dir="ltr" data-setdir="false">{"activity":"Make a simple musical instrument","type":"music","participants":1,"price:0.4,"link":"","key":"7091374","accessibility":0.25}<span style="color: rgb(0, 0, 0); font-family: Helvetica Neue, Helvetica, Arial, sans-serif;">^M</span></div><div dir="ltr" data-setdir="false">parseHeaders: parse ICAP headers</div><div dir="ltr" data-setdir="false"><span style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; color: rgb(38, 40, 42);">parsePart: have 144 head bytes to parse; state: 0</span><br clear="none" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; color: rgb(38, 40, 42);"><span style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; color: rgb(38, 40, 42);">parsePart: head parsing result: 0 detail: 600</span></div><div><span style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; color: rgb(38, 40, 42);"><br></span></div></div></div><div><br></div>
</div><div id="yahoo_quoted_1267478826" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, March 18, 2024 at 11:21:02 PM EDT, Alex Rousskov <rousskov@measurement-factory.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On 2024-03-18 18:46, Arun Kumar wrote:<div class="yqt9902438220" id="yqtfd12553"><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</div><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" 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.<div class="yqt9902438220" id="yqtfd25648"><br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>