diff options
| author | Razvan Cojocaru <rcojocaru@bitdefender.com> | 2015-08-21 10:29:05 +0200 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2015-08-24 12:34:17 +0200 |
| commit | 62f306ff34f569020ce54451da7c841d162710ac (patch) | |
| tree | 573f8b2cb9fdc34e6d06d35ac0fb8c90f1b4b6d9 /docs/KNOWN_BUGS | |
| parent | 36f6f6f4f2331dbd276a8455ecdafc16aceecb80 (diff) | |
getinfo: added CURLINFO_ACTIVESOCKET
This patch addresses known bug #76, where on 64-bit Windows SOCKET is 64
bits wide, but long is only 32, making CURLINFO_LASTSOCKET unreliable.
Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Diffstat (limited to 'docs/KNOWN_BUGS')
| -rw-r--r-- | docs/KNOWN_BUGS | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 345dc45d5..e0cd8e6ec 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -63,11 +63,6 @@ may have been fixed since this was written! any file at all. Like when using FTP. http://curl.haxx.se/bug/view.cgi?id=1063 -76. The SOCKET type in Win64 is 64 bits large (and thus so is curl_socket_t on - that platform), and long is only 32 bits. It makes it impossible for - curl_easy_getinfo() to return a socket properly with the CURLINFO_LASTSOCKET - option as for all other operating systems. - 75. NTLM authentication involving unicode user name or password only works properly if built with UNICODE defined together with the WinSSL/schannel backend. The original problem was mentioned in: |