aboutsummaryrefslogtreecommitdiff
path: root/docs
AgeCommit message (Collapse)Author
2007-02-10darned tab completion on a late evening... :-PDaniel Stenberg
2007-02-10minor updates to reflect reality betterDaniel Stenberg
2007-02-10file:// transfers are blockingDaniel Stenberg
2007-02-05- Michael Wallner provided a patch that adds support for CURLOPT_TIMEOUT_MSDaniel Stenberg
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.
2007-02-03some additional infoDaniel Stenberg
2007-01-28recent contributorsDaniel Stenberg
2007-01-27- David McCreedy fixed the Curl command line tool for HTTP on non-ASCIIDaniel Stenberg
platforms.
2007-01-26updated mingw build instructions for libssh2.Gunter Knauf
2007-01-25- Added the --libcurl [file] option to curl. Append this option to anyDaniel Stenberg
ordinary curl command line, and you will get a libcurl-using source code written to the file that does the equivalent operation of what your command line operation does!
2007-01-17clarify the INFILESIZE option(s)Daniel Stenberg
2007-01-09corrected exampleDaniel Stenberg
2007-01-08no suprise really, but it works fine on SH4 as well...Daniel Stenberg
2007-01-05- Linus Nielsen Feltzing introduced the --ftp-ssl-ccc command line option toDaniel Stenberg
curl that uses the new CURLOPT_FTP_SSL_CCC option in libcurl. If enabled, it will make libcurl shutdown SSL/TLS after the authentication is done on a FTP-SSL operation.
2007-01-02- Victor Snezhko helped us fix bug report #1603712Daniel Stenberg
(http://curl.haxx.se/bug/view.cgi?id=1603712) (known bug #36) --limit-rate (CURLOPT_MAX_SEND_SPEED_LARGE and CURLOPT_MAX_RECV_SPEED_LARGE) are broken on Windows (since 7.16.0, but that's when they were introduced as previous to that the limiting logic was made in the application only and not in the library). It was actually also broken on select()-based systems (as apposed to poll()) but we haven't had any such reports. We now use select(), Sleep() or delay() properly to sleep a while without waiting for anything input or output when the rate limiting is activated with the easy interface.
2006-12-31curl_easy_cleanup kills this memory tooDaniel Stenberg
2006-12-21CURLOPT_CAPATH is OpenSSL-onlyDaniel Stenberg
2006-12-19* removed the SSH-based protocols as they are now being implementedDaniel Stenberg
* added mentioning of doing the stunnel equivalent ourselves for the test suite * spell-check
2006-12-1937. Having more than one connection to the same host when doing NTLMDaniel Stenberg
authentication (with performs multiple "passes" and authenticates a connection rather than a HTTP request), and particularly when using the multi interface, there's a risk that libcurl will re-use a wrong connection when doing the different passes in the NTLM negotiation and thus fail to negotiate (in seemingly mysterious ways). 36. --limit-rate (CURLOPT_MAX_SEND_SPEED_LARGE and CURLOPT_MAX_RECV_SPEED_LARGE) are broken on Windows (since 7.16.0, but that's when they were introduced as previous to that the limiting logic was made in the application only and not in the library). This problem is easily repeated and it takes a Windows person to fire up his/hers debugger in order to fix. http://curl.haxx.se/bug/view.cgi?id=1603712
2006-12-14minor syntax mistakeDaniel Stenberg
2006-12-067.16.1 knows SFTP tooDaniel Stenberg
2006-12-06clarify --limit-rate somewhat: it might send away/receive chunks of date inDaniel Stenberg
temporarily higher speeds than requested, but the given limiting is considered "over time" and is an average
2006-12-05Sh Diao reported that CURLOPT_CLOSEPOLICY doesn't work, and indeed, there isDaniel Stenberg
no code present in the library that receives the option. Since it was not possible to use, we know that no current users exist and thus we simply removed it from the docs and made the code always use the default path of the code.
2006-12-05fixed in CVSDaniel Stenberg
2006-11-19Frank Teo provided an updated, mostly docs changedDaniel Stenberg
2006-11-18new ruby binding, new tclcurl releaseDaniel Stenberg
2006-11-08ok stop using old and deprecated optionsDaniel Stenberg
2006-11-03SCP support addedDaniel Stenberg
2006-11-03Olaf Stueben provided a patch that I edited slightly. It fixes the notoriousDaniel Stenberg
KNOWN_BUGS #25, which happens when a proxy closes the connection when libcurl has sent CONNECT, as part of an authentication negotiation. Starting now, libcurl will re-connect accordingly and continue the authentication as it should.
2006-11-03initial SCP support is now addedDaniel Stenberg
2006-11-02mention the new optionsDaniel Stenberg
2006-11-02James Housley brought support for SCP transfersDaniel Stenberg
2006-10-30add contributors from the 7.16.0 releaseDaniel Stenberg
2006-10-29Compiler warning fixYang Tse
2006-10-25a Smalltalk bindingDaniel Stenberg
2006-10-25Fixed CURLOPT_FAILONERROR to return CURLE_HTTP_RETURNED_ERROR even for theDaniel Stenberg
case when 401 or 407 are returned, *IF* no auth credentials have been given. The CURLOPT_FAILONERROR option is not possible to make fool-proof for 401 and 407 cases when auth credentials is given, but we've now covered this somewhat more. You might get some amounts of headers transferred before this situation is detected, like for when a "100-continue" is received as a response to a POST/PUT and a 401 or 407 is received immediately afterwards. Added test 281 to verify this change.
2006-10-21Armel Asselin separated CA cert verification problems from problems withDaniel Stenberg
reading the (local) CA cert file to let users easier pinpoint the actual problem. CURLE_SSL_CACERT_BADFILE (77) is the new libcurl error code.
2006-10-20made the arrow for 'Send SSL data' point in the right direction!Daniel Stenberg
2006-10-18the "work in progress" for #25 was ditched a long time agoDaniel Stenberg
2006-10-13Added comments about checking return code and the maxfd counterDaniel Stenberg
2006-10-12ghiper now uses the timer callback in the multi interfaceDaniel Stenberg
2006-10-12clarify moreDaniel Stenberg
2006-10-12Starting now, adding an easy handle to a multi stack that was already addedDaniel Stenberg
to a multi stack will cause CURLM_BAD_EASY_HANDLE to get returned.
2006-10-12deleted #19 since it concerted FTP third party transfers and they are no longerDaniel Stenberg
supported
2006-10-12we've cut out third party transfersDaniel Stenberg
2006-10-12point out the sslcert web page for -k/--insecureDaniel Stenberg
2006-10-12Jeff Pohlmeyer has been working with the hiperfifo.c example source code,Daniel Stenberg
and while doing so it became apparent that the current timeout system for the socket API really was a bit awkward since it become quite some work to be sure we have the correct timeout set. Jeff then provided the new CURLMOPT_TIMERFUNCTION that is yet another callback the app can set to get to know when the general timeout time changes and thus for an application like hiperfifo.c it makes everything a lot easier and nicer. There's a CURLMOPT_TIMERDATA option too of course in good old libcurl tradition.
2006-10-10repair id stringDaniel Stenberg
2006-10-10Added ghiper.c, Jeff Pohlmeyer's example code using the curl_multi_socket()Daniel Stenberg
API with glib2
2006-10-09changed the wording about removal of internal headers with -HDaniel Stenberg
2006-10-08slightly improvedDaniel Stenberg