[8/9] winhttp: Don't try to read data when the server response is HTTP_STATUS_NO_CONTENT or HTTP_STATUS_NOT_MODIFIED.

[Hans Leidekker]

These failures are unrelated. They should be fixed by the last patch in
this series.

On Tue, Dec 9, 2014 at 2:41 PM, Marvin <testbot at winehq.org> wrote:

> Hi,
>
> While running your changed tests on Windows, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> Full results can be found at
> https://testbot.winehq.org/JobDetails.pl?Key=10702
>
> Your paranoid android.
>
>
> === w7u (32 bit winhttp) ===
> winhttp.c:2035: Test failed: failed to receive response 12030
> winhttp.c:2039: Test failed: failed to query status code 12019
> winhttp.c:2040: Test failed: request failed unexpectedly 589826
> winhttp.c:2044: Test failed: failed to query authentication schemes 4317
> winhttp.c:2045: Test failed: got deadbeef
> winhttp.c:2046: Test failed: got deadbeef
> winhttp.c:2047: Test failed: got deadbeef
>
> === w8 (32 bit winhttp) ===
> winhttp.c:2035: Test failed: failed to receive response 12030
> winhttp.c:2039: Test failed: failed to query status code 12019
> winhttp.c:2040: Test failed: request failed unexpectedly 589826
> winhttp.c:2044: Test failed: failed to query authentication schemes 4317
> winhttp.c:2045: Test failed: got deadbeef
> winhttp.c:2046: Test failed: got deadbeef
> winhttp.c:2047: Test failed: got deadbeef
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20141209/ed14ba7b/attachment.html>