Re: [PATCH] wininet: Initialize netconn_stream's content_length

On 11/23/11 04:17, Andy Clayton wrote: On Tue, Nov 22, 2011 at 9:28 AM, Andy Clayton > wrote: Hi Jacek, On Tue, Nov 22, 2011 at 3:59 AM, Jacek Caban mailto:ja...@codeweavers.com>> wrote: This doesn't seem right. At the point where we call HT

Re: [PATCH] wininet: Initialize netconn_stream's content_length

On Tue, Nov 22, 2011 at 9:28 AM, Andy Clayton wrote: > Hi Jacek, > > On Tue, Nov 22, 2011 at 3:59 AM, Jacek Caban wrote: > >> This doesn't seem right. At the point where we call >> HTTP_ReceiveRequestData, content_length is supposed to be set based on >> response header. The bug must be somewhere

Re: [PATCH] wininet: Initialize netconn_stream's content_length

Hi Jacek, On Tue, Nov 22, 2011 at 3:59 AM, Jacek Caban wrote: > This doesn't seem right. At the point where we call > HTTP_ReceiveRequestData, content_length is supposed to be set based on > response header. The bug must be somewhere else. > Thanks for looking over my patch. So it seems then th

Re: [PATCH] wininet: Initialize netconn_stream's content_length

Hi Andy, On 11/22/11 5:49 AM, Andy Clayton wrote: The size that net_conn_read reads is limited by netconn_stream's remaining content_length, so if the content_length is zero it reads nothing. It also means that the read size it returns is 0, which typically indicates that the socket was closed.