Lines Matching +full:- +full:- +full:disable +full:- +full:ldap
16 1.5 Expect-100 meets 417
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
55 6.6 libcurl can fail to try alternatives with --proxy-any
57 6.9 SHA-256 digest not supported in Windows SSPI builds
85 11.4 HTTP test server 'connection-monitor' problems
88 12. LDAP
90 12.2 LDAP on Windows does authentication wrong?
91 12.3 LDAP on Windows does not work
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.
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
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
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:
313 https://curl.se/mail/lib-2009-10/0024.html
317 https://curl.se/mail/lib-2012-07/0073.html
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
369 When using --negotiate (or NTLM) with curl on Windows, SSL/TLS handshake
401 https://curl.se/mail/lib-2008-07/0295.html
452 prematurely. There is a half-baked (busy-looping) patch provided in the bug
453 report but it cannot be accepted as-is. See
507 11.4 HTTP test server 'connection-monitor' problems
509 The 'connection-monitor' feature of the sws HTTP test server does not work
522 12. LDAP
532 As a temporary workaround, disable referrals chasing by configuration.
538 Generic LDAP is synchronous: OK.
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
549 A simple curl command line getting "ldap://ldap.forumsys.com" returns an
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