http://bugs.winehq.org/show_bug.cgi?id=15107
--- Comment #10 from Rotem Zach rotemz@gmail.com 2008-09-03 10:55:05 --- Could be, I don't have enough experience to check it. The problem is that chrome uses async connections.
From debug: trace:winhttp:WinHttpOpen (null), 1, (null), (null), 0x10000000 From chrome code: HINTERNET internet = WinHttpOpen(NULL,
WINHTTP_ACCESS_TYPE_NO_PROXY, WINHTTP_NO_PROXY_NAME, WINHTTP_NO_PROXY_BYPASS, WINHTTP_FLAG_ASYNC);
Is it possible to hack a solution that makes chrome think it is using an async connection?