https://bugs.winehq.org/show_bug.cgi?id=37023
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Andreas Fuchs from comment #4)
Attachment 1 [details] "Test case for this issue" should however still yield different behaviours right ?
Yes, the behaviour is different. Nevertheless, as it seems to fail completely on Windows, I normally wouldn't expect that any app tries to use it - except its an issue somewhere in your testcase.
(In reply to Andreas Fuchs from comment #5)
Looking at this patch I'm sceptical. One of the points about a head-request is, that the server's answer will contain a content_length field. So I'm not sure, what wine's winhttp returns when being asked for the content_length. I _guess_ WinHttpQueryHeaders() is not a problem. Are there other ways that the content_length-field will be accessed by the application ?
As far as I know the content_length field is only used for receiving the data, when the app tries to check the header fields the corresponding entry from an internal list is used instead.