<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 27, 2017 at 11:34 AM, Alex Rousskov <span dir="ltr"><<a href="mailto:rousskov@measurement-factory.com" target="_blank">rousskov@measurement-factory.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 06/27/2017 10:11 AM, Razor Cross wrote:<br>
<span class="">> On Mon, Jun 26, 2017 at 12:06 PM, Alex Rousskov wrote:<br>
<br>
> >I suspect that the COMPLETE_NONPERSISTENT_MSG case in<br>
> >HttpStateData::<wbr>processReplyBody() should be changed to call<br>
> >StoreEntry::lengthWentBad("<wbr>missing last-chunk") when lastChunk is false<br>
> >and HttpStateData::flags.chunked is true.<br>
<br>
> We are able to reproduce the issue . If server socket is closed<br>
> after sending first chunk of data, squid is caching the partial object<br>
> even though it did not receive the remaining chunks.<br>
<br>
</span>If you are not going to fix this yourself, please consider filing a bug<br>
report, citing this email thread.<br>
<span class=""><br>
<br>
> I feel it has to<br>
> make sure that lastchunk has received before caching the data.<br>
<br>
</span>That is impossible in general (the response may be too big to buffer)<br>
but is also unnecessary in most cases (because Squid can stop caching<br>
and delete the being-cached object in-flight). My paragraph quoted above<br>
has the blueprint for a possible fix.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div>Thanks for your inputs..</div><div>I just want to hear from squid official forum/owner whether it has fixed in any recent squid releases so that we can upgrade/patch the fix.</div><div><br></div><div>- Cross</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><br></div></div>