Lines Matching +full:windows +full:- +full:remote +full:- +full:only
16 1.5 Expect-100 meets 417
24 2.11 Schannel TLS 1.2 handshake bug in old Windows versions
30 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
39 5.2 curl-config --libs contains private details
41 5.5 cannot handle Unicode arguments in non-Unicode builds on Windows
42 5.6 cygwin: make install installs curl-config.1 twice
44 5.11 configure --with-gssapi with Heimdal is ignored on macOS
46 5.13 long paths are not fully supported on Windows
47 5.14 Windows Unicode builds use homedir in current locale
48 5.15 Unicode on Windows
52 6.2 MIT Kerberos for Windows build
55 6.6 libcurl can fail to try alternatives with --proxy-any
57 6.9 SHA-256 digest not supported in Windows SSPI builds
59 6.11 Negotiate on Windows fails
70 7.12 FTPS directory listing hangs on Windows with Schannel
75 9.3 Remote recursive folder creation with SFTP
85 11.4 HTTP test server 'connection-monitor' problems
90 12.2 LDAP on Windows does authentication wrong?
91 12.3 LDAP on Windows does not work
95 13.2 Trying local ports fails on Windows
101 15.6 uses -lpthread instead of Threads::Threads
106 16. aws-sigv4
107 16.1 aws-sigv4 does not sign requests with * correctly
108 16.6 aws-sigv4 does not behave well with AWS VPC Lattice
131 1.5 Expect-100 meets 417
133 If an upload using Expect: 100-continue receives an HTTP 417 response, it
136 https://curl.se/mail/archive-2008-02/0043.html
157 server-specified DNs, the OpenSSL and GnuTLS backends behave differently.
166 2.11 Schannel TLS 1.2 handshake bug in old Windows versions
168 In old versions of Windows such as 7 and 8.1 the Schannel TLS 1.2 handshake
192 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
200 Specifying "--login-options AUTH=PLAIN" on the command line does not seem to
211 CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982
227 5.2 curl-config --libs contains private details
229 "curl-config --libs" will include details set in LDFLAGS when configure is
230 run that might be needed only for building libcurl. Further, curl-config
231 --cflags suffers from the same effects with CFLAGS/CPPFLAGS.
240 5.5 cannot handle Unicode arguments in non-Unicode builds on Windows
243 it can only be encoded properly in the Unicode character set. Windows uses
244 UTF-16 encoding for Unicode and stores it in wide characters, however curl
246 _UNICODE and UNICODE defined. And, except for Cygwin, Windows cannot use UTF-8
253 5.6 cygwin: make install installs curl-config.1 twice
261 5.11 configure --with-gssapi with Heimdal is ignored on macOS
263 ... unless you also pass --with-gssapi-libs
270 number of the Windows builds are flaky. This means that we rarely get all CI
277 5.13 long paths are not fully supported on Windows
279 curl on Windows cannot access long paths (paths longer than 260 characters).
280 However, as a workaround, the Windows path prefix \\?\ which disables all path
286 5.14 Windows Unicode builds use homedir in current locale
288 The Windows Unicode builds of curl use the current locale, but expect Unicode
289 UTF-8 encoded paths for internal use such as open, access and stat. The user's
291 UTF-8 encoded Unicode.
296 5.15 Unicode on Windows
298 Passing in a unicode filename with -o:
302 Passing in unicode character with -d:
310 NTLM authentication involving unicode user name or password only works
313 https://curl.se/mail/lib-2009-10/0024.html
317 https://curl.se/mail/lib-2012-07/0073.html
319 6.2 MIT Kerberos for Windows build
321 libcurl fails to build with MIT Kerberos for Windows (KfW) due to KfW's
327 NTLM authentication using SSPI (on Windows) when (lib)curl is running in
328 "system context" will make it use wrong(?) user name - at least when compared
335 6.6 libcurl can fail to try alternatives with --proxy-any
337 When connecting via a proxy using --proxy-any, a failure to establish an
340 --proxy-any against a proxy which advertise Negotiate and NTLM, but which
350 6.9 SHA-256 digest not supported in Windows SSPI builds
352 Windows builds of curl that have SSPI enabled use the native Windows API calls
367 6.11 Negotiate on Windows fails
369 When using --negotiate (or NTLM) with curl on Windows, SSL/TLS handshake
401 https://curl.se/mail/lib-2008-07/0295.html
434 7.12 FTPS server compatibility on Windows with Schannel
452 prematurely. There is a half-baked (busy-looping) patch provided in the bug
453 report but it cannot be accepted as-is. See
464 9.3 Remote recursive folder creation with SFTP
466 On this servers, the curl fails to create directories on the remote server
503 only. But you only have IPv4 connectivity. libcurl will correctly fail with
507 11.4 HTTP test server 'connection-monitor' problems
509 The 'connection-monitor' feature of the sws HTTP test server does not work
541 https://curl.se/mail/lib-2016-01/0101.html
543 12.2 LDAP on Windows does authentication wrong?
547 12.3 LDAP on Windows does not work
560 13.2 Trying local ports fails on Windows
562 This makes '--local-port [range]' to not work since curl cannot properly
582 15.6 uses -lpthread instead of Threads::Threads
588 The Libs.private field of the generated .pc file contains -lgcc -lgcc_s -lc
589 -lgcc -lgcc_s
605 and ;-separated flags. It had to blow up at some point. All the CMake checks
611 16. aws-sigv4
613 16.1 aws-sigv4 does not sign requests with * correctly
617 16.6 aws-sigv4 does not behave well with AWS VPC Lattice