No subject

=0D
trace:winhttp:WinHttpSetTimeouts 0x3, 0, 60000, 30000, 30000=0D
fixme:winhttp:WinHttpSetTimeouts resolve and connect timeout not supported=
=0D
trace:winhttp:addref_object 0x81ab4f8 -> refcount =3D 2=0D
trace:winhttp:grab_object handle 0x3 -> 0x81ab4f8=0D
warn:winhttp:netconn_set_timeout setsockopt failed (Chybn=C3=BD popisova=C4=
=8D souboru)=0D
warn:winhttp:netconn_set_timeout setsockopt failed (Chybn=C3=BD popisova=C4=
=8D souboru)=0D
=0D
And, from winhttp/session.c:=0D
    if (netconn_set_timeout( &request->netconn, TRUE, send )) ret =3D FALSE=
;=0D
(snip)=0D
    return ret;=0D
=0D
So I'd say the failing setsockopt is the issue.  Google tells me "Chybn=C3=
=BD=0D
popisova=C4=8D souboru" is "Bad file descriptor" in English.=0D
=0D
Looking further at the log, the handle passed to WinHttpSetTimeouts is 0x3.=
 =0D
It's created with WinHttpOpenRequest:=0D
=0D
trace:winhttp:WinHttpOpenRequest 0x2, L"GET", L"/nucleus/authToken", (null)=
,=0D
(null), (nil), 0x00800100=0D
(snip)=0D
trace:winhttp:WinHttpOpenRequest returning 0x3=0D
=0D
Note that the flags include WINHTTP_FLAG_SECURE (0x00800000).  Looking at=
=0D
WinHttpOpenRequest,=0D
=0D
    if (!netconn_init( &request->netconn, request->hdr.flags &=0D
WINHTTP_FLAG_SECURE )) goto end;=0D
=0D
That is, it calls netconn_init, with secure =3D TRUE since WINHTTP_FLAG_SEC=
URE=0D
was set.  From net.c:=0D
=0D
BOOL netconn_init( netconn_t *conn, BOOL secure )=0D
{=0D
    conn->socket =3D -1;=0D
    if (!secure) return TRUE;=0D
=0D
#if defined(SONAME_LIBSSL) && defined(SONAME_LIBCRYPTO)=0D
    if (libssl_handle) return TRUE;=0D
=0D
So, conn->socket is currently set to -1, so setsockopt will fail.  I'd gues=
s=0D
that WinHttpSetTimeouts should still succeed in this case, perhaps by stori=
ng=0D
the timeouts and calling setsockopt when the connection is actually created=
.=0D
=0D
-- =0D
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=3Demail=0D
Do not reply to this email, post in Bugzilla using the=0D
above URL to reply.=0D
------- You are receiving this mail because: -------=0D
You are watching all bug changes.=