https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- 0144:trace:winhttp:WinHttpSetOption 0x1, 84, 0x7f86efc9fa80, 4 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x1 -> 0x3a073ec0 0144:trace:winhttp:session_set_option 0xa80 0144:trace:winhttp:release_object object 0x3a073ec0 refcount = 1
It sets the SECURE_PROTOCOLS option on the session handle, which succeeds.
0144:trace:winhttp:WinHttpConnect 0x1, L"api.bethesda.net", 443, 0 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x1 -> 0x3a073ec0 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 3 0144:trace:winhttp:addref_object 0x3a037e00 -> refcount = 2 0144:trace:winhttp:release_object object 0x3a037e00 refcount = 1 0144:trace:winhttp:release_object object 0x3a073ec0 refcount = 2 0144:trace:winhttp:WinHttpConnect returning 0x2 0144:trace:winhttp:WinHttpSetOption 0x2, 84, 0x7f86efc9fa80, 4 0144:trace:winhttp:addref_object 0x3a037e00 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x2 -> 0x3a037e00 0144:fixme:winhttp:set_option unimplemented option 84
Here it tries to do the same with the connect handle but we don't support that.