Lines Matching +full:- +full:- +full:with +full:- +full:gssapi
16 1.5 Expect-100 meets 417
19 2.1 IMAPS connection fails with rustls error
20 2.3 Unable to use PKCS12 certificate with Secure Transport
22 2.5 Client cert handling with Issuer DN differs between backends
23 2.7 Client cert (MTLS) issues with Schannel
25 2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel
30 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
39 5.2 curl-config --libs contains private details
40 5.3 building for old macOS fails with gcc
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
54 6.5 NTLM does not support password with § character
55 6.6 libcurl can fail to try alternatives with --proxy-any
57 6.9 SHA-256 digest not supported in Windows SSPI builds
60 6.12 cannot use Secure Transport with Crypto Token Kit
66 7.3 FTP with NOBODY and FAILONERROR
67 7.4 FTP with ACCT
69 7.11 FTPS upload data loss with TLS 1.3
70 7.12 FTPS directory listing hangs on Windows with Schannel
75 9.3 Remote recursive folder creation with SFTP
83 11.1 gssapi library name + version is missing in curl_version_info()
85 11.4 HTTP test server 'connection-monitor' problems
99 15.2 support build with GnuTLS
100 15.3 unusable tool_hugehelp.c with MinGW
101 15.6 uses -lpthread instead of Threads::Threads
104 15.13 CMake build with MIT Kerberos does not work
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
140 2.1 IMAPS connection fails with rustls error
144 2.3 Unable to use PKCS12 certificate with Secure Transport
150 libcurl calls SecPKCS12Import with the PKCS#12 client certificate, but that
154 2.5 Client cert handling with Issuer DN differs between backends
157 server-specified DNs, the OpenSSL and GnuTLS backends behave differently.
162 2.7 Client cert (MTLS) issues with Schannel
174 2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel
192 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
194 You have to tell libcurl not to expect a body, when dealing with one line
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.
233 5.3 building for old macOS fails with gcc
240 5.5 cannot handle Unicode arguments in non-Unicode builds on Windows
244 UTF-16 encoding for Unicode and stores it in wide characters, however curl
245 and libcurl are not equipped for that at the moment except when built with
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
289 UTF-8 encoded paths for internal use such as open, access and stat. The user's
291 UTF-8 encoded Unicode.
298 Passing in a unicode filename with -o:
302 Passing in unicode character with -d:
311 properly if built with UNICODE defined together with the Schannel
313 https://curl.se/mail/lib-2009-10/0024.html
317 https://curl.se/mail/lib-2012-07/0073.html
321 libcurl fails to build with MIT Kerberos for Windows (KfW) due to KfW's
328 "system context" will make it use wrong(?) user name - at least when compared
331 6.5 NTLM does not support password with § character
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
354 with SEC_E_QOP_NOT_SUPPORTED which causes curl to fail with CURLE_AUTH_ERROR.
369 When using --negotiate (or NTLM) with curl on Windows, SSL/TLS handshake
375 6.12 cannot use Secure Transport with Crypto Token Kit
397 7.3 FTP with NOBODY and FAILONERROR
400 with FTP to detect if a file exists or not, but it is not working:
401 https://curl.se/mail/lib-2008-07/0295.html
403 7.4 FTP with ACCT
417 7.11 FTPS upload data loss with TLS 1.3
434 7.12 FTPS server compatibility on Windows with Schannel
436 FTPS is not widely used with the Schannel TLS backend and so there may be more
442 If you encounter an issue connecting to your server via FTPS with the latest
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
475 transmission, curl will be stuck, even if curl is configured with a timeout.
494 11.1 gssapi library name + version is missing in curl_version_info()
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
562 This makes '--local-port [range]' to not work since curl cannot properly
576 15.2 support build with GnuTLS
578 15.3 unusable tool_hugehelp.c with MinGW
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
600 15.13 CMake build with MIT Kerberos does not work
603 try_compile started respecting the CMAKE_EXE_FLAGS. The code dealing with
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
639 Infinite retries with 2 parallel requests on one connection receiving GOAWAY
640 with ENHANCE_YOUR_CALM error code.