- Feb 13, 2007
- Feb 12, 2007
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/
-
Daniel Stenberg authored
to the debug callback. - Shmulik Regev added CURLOPT_HTTP_CONTENT_DECODING and CURLOPT_HTTP_TRANSFER_DECODING that if set to zero will disable libcurl's internal decoding of content or transfer encoded content. This may be preferable in cases where you use libcurl for proxy purposes or similar. The command line tool got a --raw option to disable both at once.
-
Daniel Stenberg authored
as a bugfix here ;-)
-
Daniel Stenberg authored
that has an easy handle present in the "closure" list pending closure.
-
Daniel Stenberg authored
to primarily be used for the autobuilds to know from what point in time a particular tarball is, and thus what changes it contains (or not).
-
- Feb 11, 2007
-
-
Daniel Stenberg authored
instead focus on explaining on how the libs differ from each other
-
Daniel Stenberg authored
-
- Feb 10, 2007
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Feb 09, 2007
-
-
Yang Tse authored
list of source files for those tests that use it. Otherwise testutil.h might not be found by the compiler.
-
Yang Tse authored
part of the official libcurl API http://curl.haxx.se/lxr/source/lib/README.curlx The documented way of using them would be to use timeval.c as a source code file. The above described method works very well when statically linking libcurl and apps, test programs, but has several drawbacks when you build a true shared libcurl (i.e. Name space clash at linkage stage as functions are defined more than once. Windows makefiles are not capable of handling this system of source-level sharing) So... Now testutil.h and testutil.c define and implement tutil_tvnow and tutil_tvdiff which replace curlx_tvnow and curlx_tvdiff for the libtest programs. Doing this we avoid the above described problems, and the code in the testsuite does not impose the need to keep those functions public in libcurl even when not part of the API.
-
Yang Tse authored
part of the official libcurl API http://curl.haxx.se/lxr/source/lib/README.curlx The documented way of using them would be to use timeval.c as a source code file. The above described method works very well when statically linking libcurl and apps, test programs, but has several drawbacks when you build a true shared libcurl (i.e. Name space clash at linkage stage as functions are defined more than once. Windows makefiles are not capable of handling this system of source-level sharing) So... Now testutil.h and testutil.c define and implement tutil_tvnow and tutil_tvdiff which replace curlx_tvnow and curlx_tvdiff for the libtest programs. Doing this we avoid the above described problems, and the code in the testsuite does not impose the need to keep those functions public in libcurl even when not part of the API.
-
- Feb 08, 2007
- Feb 07, 2007
-
-
Daniel Stenberg authored
-
Yang Tse authored
-
Yang Tse authored
assumes that pointers can only point to an object of the same type.
-
Yang Tse authored
*) Update CURL_CC_DEBUG_OPTS from curl's script
-
- Feb 06, 2007
-
-
Gisle Vanem authored
-
Gisle Vanem authored
-
Gisle Vanem authored
Include <process.h> for getpid() in ares_init.c.
-
Gisle Vanem authored
-
Gisle Vanem authored
Added 'optind' and 'optarg' as in adig.c.
-
Gisle Vanem authored
-
Yang Tse authored
-
Yang Tse authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Yang Tse authored
-
- Feb 05, 2007
-
-
Daniel Stenberg authored
and CURLOPT_CONNECTTIMEOUT_MS that, as their names should hint, do the timeouts with millisecond resolution instead. The only restriction to that is the alarm() (sometimes) used to abort name resolves as that uses full seconds. I fixed the FTP response timeout part of the patch. Internally we now count and keep the timeouts in milliseconds but it also means we multiply set timeouts with 1000. The effect of this is that no timeout can be set to more than 2^31 milliseconds (on 32 bit systems), which equals 24.86 days. We probably couldn't before either since the code did *1000 on the timeout values on several places already.
-
Gisle Vanem authored
-
Yang Tse authored
-
Yang Tse authored
-