http://bugs.winehq.org/show_bug.cgi?id=16165
--- Comment #8 from Paul "TBBle" Hampson Paul.Hampson@Pobox.com 2008-12-30 11:08:54 --- Ignore comment 7, that patch has already been applied. The problem is that the caller of winhttp is incorrectly getting port 0 back from WinHttpCrackUrl and then is passing that 0 to WinHttpConnect. It's definately WinHttpCrackUrl that needs to be fixed.
I'm surprised this hasn't shown up anywhere else, but I haven't found any other bugs that suggest the same issue has been hit.