Lines Matching full:libcurl
40 - [Structs in libcurl](#structs)
69 We write curl and libcurl to compile with C89 compilers. On 32bit and up
70 machines. Most of libcurl assumes more or less POSIX compliance but that's
73 We write libcurl to build and work with lots of third party tools, and we
169 (See `LIBCURL-STRUCTS` for a separate document describing all major internal
173 function that libcurl offers to applications. All of those functions are
180 the socket layer on windows machines. libcurl itself has no "global" scope.
237 If this DO function fails and the connection is being re-used, libcurl will
276 it can be called to make sure that libcurl doesn't keep too many
385 The persistent connection support in libcurl requires some considerations on
397 - When libcurl is told to perform a transfer, it first checks for an already
403 open. Particular options may tell libcurl not to, and protocols may signal
417 interface work as good as possible, no low-level functions within libcurl
429 to better fit the libcurl protocol family.
435 Originally libcurl supported SSLeay for SSL/TLS transports, but that was then
438 in future libcurl versions.
442 SSL functions we must use from within libcurl. vtls is then crafted to use
450 libcurl must use a `Curl_` prefix if they're
461 I've made things simple. Almost every function in libcurl returns a CURLcode,
478 that makes it easier to keep a solid API/ABI over time. See docs/libcurl/ABI
557 libcurl can be built to do name resolves asynchronously, using either the
564 ### Build libcurl to use a c-ares
576 Next was libcurl. I opened lib/config-win32.h and I added a:
582 Lastly, I also changed libcurl to be single-threaded rather than
592 curl_off_t is a data type provided by the external libcurl include
600 The libcurl source code offers a few functions by source only. They are not
601 part of the official libcurl API, but the source files might be useful for
634 future libcurl release. They will then only become available as curlx_
680 The 'deflate' and 'gzip' content encoding are supported by libcurl. Both
684 ## The libcurl interface
686 To cause libcurl to request a content encoding use:
692 Currently, libcurl only understands how to process responses that use the
696 "compress" or methods, libcurl will return an error indicating that the
726 is defined if libcurl is built to use c-ares for asynchronous name
731 is defined if libcurl is built to use threading for asynchronous name
737 libcurl is not built to use an asynchronous resolver, `CURLRES_SYNCH` is
768 Rebuild libcurl with -DCURLDEBUG (usually, rerunning configure with
771 libcurl with the debug option (usually -g to the compiler) so that debugging
784 and that you link with the same libcurl you built for this purpose as
791 Make your program exit and use the proper libcurl cleanup functions etc. So
803 If this doesn't produce any output, no leak was detected in libcurl. Then
815 from libcurl about what file descriptors libcurl waits for what action
819 libcurl and informs that there was action on this particular socket and
820 libcurl can then act on that socket/transfer only and not care about
828 We also added a timer callback that makes libcurl call the application when
844 To make libcurl able to report plain sockets in the socket callback, we had
853 Structs in libcurl
866 'connectdata' struct. When a transfer is about to be made, libcurl will
878 that same multi handle. libcurl always uses multi so ->multi *will* point to
886 The libcurl source code generally use the name 'data' for the variable that
895 A general idea in libcurl is to keep connections around in a connection
909 Functions in libcurl will assume that connectdata->data points to the
912 As a special complexity, some protocols supported by libcurl require a
917 down a particular connection. For this purpose, libcurl holds a special
925 The libcurl source code generally use the name 'conn' for the variable that
961 The libcurl source code generally use the name 'multi' for the variable that
966 Each unique protocol that is supported by libcurl needs to provide at least
972 from a single array which is scanned through when a URL is given to libcurl
1060 The libcurl share API allocates a `Curl_share` struct, exposed to the
1082 [1]: http://curl.haxx.se/libcurl/c/curl_easy_setopt.html
1083 [2]: http://curl.haxx.se/libcurl/c/curl_easy_init.html
1086 [5]: http://curl.haxx.se/libcurl/c/CURLOPT_ACCEPT_ENCODING.html
1088 [7]: http://curl.haxx.se/libcurl/c/curl_multi_socket_action.html
1089 [8]: http://curl.haxx.se/libcurl/c/curl_multi_timeout.html
1090 [9]: http://curl.haxx.se/libcurl/c/curl_multi_setopt.html
1091 [10]: http://curl.haxx.se/libcurl/c/CURLMOPT_TIMERFUNCTION.html
1092 [11]: http://curl.haxx.se/libcurl/c/curl_multi_perform.html
1093 [12]: http://curl.haxx.se/libcurl/c/curl_multi_fdset.html
1094 [13]: http://curl.haxx.se/libcurl/c/curl_multi_add_handle.html
1095 [14]: http://curl.haxx.se/libcurl/c/curl_multi_info_read.html
