Lines Matching +full:- +full:- +full:with +full:- +full:gssapi
17 2.1 IMAPS connection fails with Rustls error
18 2.3 Unable to use PKCS12 certificate with Secure Transport
20 2.5 Client cert handling with Issuer DN differs between backends
21 2.7 Client cert (MTLS) issues with Schannel
23 2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel
34 4.1 -T /dev/stdin may upload with an incorrect content length
35 4.2 -T - always uploads chunked
39 5.2 curl-config --libs contains private details
41 5.6 Cygwin: make install installs curl-config.1 twice
42 5.11 configure --with-gssapi with Heimdal is ignored on macOS
50 6.5 NTLM does not support password with § character
51 6.6 libcurl can fail to try alternatives with --proxy-any
54 6.9 SHA-256 digest not supported in Windows SSPI builds
57 6.12 cannot use Secure Transport with Crypto Token Kit
61 7.4 FTP with ACCT
62 7.12 FTPS directory listing hangs on Windows with Schannel
67 9.3 Remote recursive folder creation with SFTP
74 11.1 gssapi library name + version is missing in curl_version_info()
77 11.4 HTTP test server 'connection-monitor' problems
95 15.2 support build with GnuTLS
96 15.3 unusable tool_hugehelp.c with MinGW
97 15.6 uses -lpthread instead of Threads::Threads
99 15.13 CMake build with MIT Kerberos does not work
101 16. aws-sigv4
102 16.2 aws-sigv4 does not handle multipart/form-data correctly
103 16.3 aws-sigv4 has problems with particular URLs
104 16.6 aws-sigv4 does not behave well with AWS VPC Lattice
125 2.1 IMAPS connection fails with Rustls error
129 2.3 Unable to use PKCS12 certificate with Secure Transport
135 libcurl calls SecPKCS12Import with the PKCS#12 client certificate, but that
139 2.5 Client cert handling with Issuer DN differs between backends
142 server-specified DNs, the OpenSSL and GnuTLS backends behave differently.
147 2.7 Client cert (MTLS) issues with Schannel
159 2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel
183 Specifying "--login-options AUTH=PLAIN" on the command line does not seem to
194 CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982
200 4.1 -T /dev/stdin may upload with an incorrect content length
202 -T stats the path to figure out its size in bytes to use it as Content-Length
205 The problem with that is that, on BSDs and some other UNIXes (not Linux),
206 open(path) may not give you a file descriptor with a 0 offset from the start
211 4.2 -T - always uploads chunked
214 regular file in this case, and that it can do a non-chunked upload, like it
215 would do if you used -T file.
229 5.2 curl-config --libs contains private details
231 "curl-config --libs" include details set in LDFLAGS when configure is run
232 that might be needed only for building libcurl. Further, curl-config --cflags
233 suffers from the same effects with CFLAGS/CPPFLAGS.
237 Compiling latest curl on HP-UX and linking against a custom OpenSSL (which is
243 5.6 Cygwin: make install installs curl-config.1 twice
247 5.11 configure --with-gssapi with Heimdal is ignored on macOS
249 ... unless you also pass --with-gssapi-libs
274 Passing in a Unicode filename with -o:
278 Passing in Unicode character with -d:
285 UTF-8 encoded paths for internal use such as open, access and stat. The
287 not as UTF-8 encoded Unicode.
292 Cannot handle Unicode arguments in non-Unicode builds on Windows
296 UTF-16 encoding for Unicode and stores it in wide characters, however curl
297 and libcurl are not equipped for that at the moment except when built with
298 _UNICODE and UNICODE defined. Except for Cygwin, Windows cannot use UTF-8 as
308 properly if built with UNICODE defined together with the Schannel backend.
310 https://curl.se/mail/lib-2009-10/0024.html
314 https://curl.se/mail/lib-2012-07/0073.html
320 libcurl fails to build with MIT Kerberos for Windows (KfW) due to KfW's
327 "system context" makes it use wrong(?) username - at least when compared to
330 6.5 NTLM does not support password with § character
334 6.6 libcurl can fail to try alternatives with --proxy-any
336 When connecting via a proxy using --proxy-any, a failure to establish an
339 --proxy-any against a proxy which advertise Negotiate and NTLM, but which
351 Running test 2077 and 2078 with curl built to do GSS with Heimdal causes
356 6.9 SHA-256 digest not supported in Windows SSPI builds
360 with SEC_E_QOP_NOT_SUPPORTED which causes curl to fail with CURLE_AUTH_ERROR.
375 When using --negotiate (or NTLM) with curl on Windows, SSL/TLS handshake
381 6.12 cannot use Secure Transport with Crypto Token Kit
391 7.4 FTP with ACCT
397 7.12 FTPS server compatibility on Windows with Schannel
399 FTPS is not widely used with the Schannel TLS backend and so there may be
405 If you encounter an issue connecting to your server via FTPS with the latest
415 prematurely. There is a half-baked (busy-looping) patch provided in the bug
416 report but it cannot be accepted as-is. See
427 9.3 Remote recursive folder creation with SFTP
438 transmission, curl is stuck, even if curl is configured with a timeout.
452 11.1 gssapi library name + version is missing in curl_version_info()
461 when you only have IPv4 connectivity. libcurl fails with
467 When adding an OpenBSD job with tests to GHA, some tests consistently fail
472 11.4 HTTP test server 'connection-monitor' problems
474 The 'connection-monitor' feature of the sws HTTP test server does not work
502 Test 165 disabled when built with WinIDN.
506 When curl has been built with specific features or protocols disabled,
507 setting such options with curl_easy_setopt() should rather return
532 https://curl.se/mail/lib-2016-01/0101.html
553 This makes '--local-port [range]' to not work since curl cannot properly
567 15.6 uses -lpthread instead of Threads::Threads
573 The Libs.private field of the generated .pc file contains -lgcc -lgcc_s -lc
574 -lgcc -lgcc_s
578 15.13 CMake build with MIT Kerberos does not work
581 try_compile started respecting the CMAKE_EXE_FLAGS. The code dealing with
583 and ;-separated flags. It had to blow up at some point. All the CMake checks
589 16. aws-sigv4
591 16.2 aws-sigv4 does not handle multipart/form-data correctly
595 16.3 aws-sigv4 has problems with particular URLs
599 16.6 aws-sigv4 does not behave well with AWS VPC Lattice
621 Infinite retries with 2 parallel requests on one connection receiving GOAWAY
622 with ENHANCE_YOUR_CALM error code.
633 See https://curl.se/mail/lib-2024-05/0026.html and
644 The transfer ends with error "QUIC connection is draining".