summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Ian Turner fixed the libcurl.m4 macro's support for --with-libcurl.Daniel Stenberg2007-02-191-1/+2
| | | | AC_PATH_PROG was not used properly.
* - Robson Braga Araujo made passive FTP transfers work with SOCKS (both 4 andDaniel Stenberg2007-02-191-5/+8
| | | | 5).
* - Jeff Pohlmeyer identified two problems: first a rather obscure problem withDaniel Stenberg2007-02-181-3/+0
| | | | | | | | | the multi interface and connection re-use that could make a curl_multi_remove_handle() ruin a pointer in another handle. The second problem was less of an actual problem but more of minor quirk: the re-using of connections wasn't properly checking if the connection was marked for closure.
* Added --ftp-ssl-ccc issue.Dan Fandrich2007-02-141-0/+4
|
* Rob Crittenden added support for NSS (Network Security Service) for theDaniel Stenberg2007-02-127-14/+55
| | | | SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/
* - Shmulik Regev fixed so that the final CRLF of HTTP response headers are sentDaniel Stenberg2007-02-122-2/+17
| | | | | | | | | | 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.
* updated with recent info and cut out some of the more speculating parts andDaniel Stenberg2007-02-111-72/+37
| | | | instead focus on explaining on how the libs differ from each other
* updatedDaniel Stenberg2007-02-112-17/+19
|
* darned tab completion on a late evening... :-PDaniel Stenberg2007-02-101-1/+1
|
* minor updates to reflect reality betterDaniel Stenberg2007-02-101-15/+12
|
* file:// transfers are blockingDaniel Stenberg2007-02-101-0/+1
|
* - Michael Wallner provided a patch that adds support for CURLOPT_TIMEOUT_MSDaniel Stenberg2007-02-051-1/+9
| | | | | | | | | | | | | 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.
* some additional infoDaniel Stenberg2007-02-031-2/+21
|
* recent contributorsDaniel Stenberg2007-01-281-0/+15
|
* - David McCreedy fixed the Curl command line tool for HTTP on non-ASCIIDaniel Stenberg2007-01-271-0/+12
| | | | platforms.
* updated mingw build instructions for libssh2.Gunter Knauf2007-01-261-6/+18
|
* - Added the --libcurl [file] option to curl. Append this option to anyDaniel Stenberg2007-01-251-1/+7
| | | | | | 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!
* clarify the INFILESIZE option(s)Daniel Stenberg2007-01-171-0/+6
|
* corrected exampleDaniel Stenberg2007-01-091-1/+3
|
* no suprise really, but it works fine on SH4 as well...Daniel Stenberg2007-01-081-0/+1
|
* - Linus Nielsen Feltzing introduced the --ftp-ssl-ccc command line option toDaniel Stenberg2007-01-052-2/+16
| | | | | | 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.
* - Victor Snezhko helped us fix bug report #1603712Daniel Stenberg2007-01-021-7/+0
| | | | | | | | | | | (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.
* curl_easy_cleanup kills this memory tooDaniel Stenberg2006-12-311-1/+2
|
* CURLOPT_CAPATH is OpenSSL-onlyDaniel Stenberg2006-12-211-8/+8
|
* * removed the SSH-based protocols as they are now being implementedDaniel Stenberg2006-12-191-5/+6
| | | | | * added mentioning of doing the stunnel equivalent ourselves for the test suite * spell-check
* 37. Having more than one connection to the same host when doing NTLMDaniel Stenberg2006-12-191-0/+14
| | | | | | | | | | | | | | | 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
* minor syntax mistakeDaniel Stenberg2006-12-141-1/+1
|
* 7.16.1 knows SFTP tooDaniel Stenberg2006-12-061-2/+2
|
* clarify --limit-rate somewhat: it might send away/receive chunks of date inDaniel Stenberg2006-12-061-0/+4
| | | | | temporarily higher speeds than requested, but the given limiting is considered "over time" and is an average
* Sh Diao reported that CURLOPT_CLOSEPOLICY doesn't work, and indeed, there isDaniel Stenberg2006-12-051-12/+3
| | | | | | | 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.
* fixed in CVSDaniel Stenberg2006-12-051-4/+0
|
* Frank Teo provided an updated, mostly docs changedDaniel Stenberg2006-11-191-2/+15
|
* new ruby binding, new tclcurl releaseDaniel Stenberg2006-11-181-2/+2
|
* ok stop using old and deprecated optionsDaniel Stenberg2006-11-081-7/+4
|
* SCP support addedDaniel Stenberg2006-11-031-2/+2
|
* Olaf Stueben provided a patch that I edited slightly. It fixes the notoriousDaniel Stenberg2006-11-031-5/+0
| | | | | | | 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.
* initial SCP support is now addedDaniel Stenberg2006-11-031-3/+2
|
* mention the new optionsDaniel Stenberg2006-11-021-1/+12
|
* James Housley brought support for SCP transfersDaniel Stenberg2006-11-021-1/+6
|
* add contributors from the 7.16.0 releaseDaniel Stenberg2006-10-301-0/+9
|
* Compiler warning fixYang Tse2006-10-291-1/+8
|
* a Smalltalk bindingDaniel Stenberg2006-10-251-0/+5
|
* Fixed CURLOPT_FAILONERROR to return CURLE_HTTP_RETURNED_ERROR even for theDaniel Stenberg2006-10-252-0/+12
| | | | | | | | | | | | | 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.
* Armel Asselin separated CA cert verification problems from problems withDaniel Stenberg2006-10-211-1/+3
| | | | | 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.
* made the arrow for 'Send SSL data' point in the right direction!Daniel Stenberg2006-10-201-3/+3
|
* the "work in progress" for #25 was ditched a long time agoDaniel Stenberg2006-10-181-2/+1
|
* Added comments about checking return code and the maxfd counterDaniel Stenberg2006-10-137-0/+27
|
* ghiper now uses the timer callback in the multi interfaceDaniel Stenberg2006-10-122-16/+17
|
* clarify moreDaniel Stenberg2006-10-121-1/+4
|
* Starting now, adding an easy handle to a multi stack that was already addedDaniel Stenberg2006-10-121-1/+3
| | | | to a multi stack will cause CURLM_BAD_EASY_HANDLE to get returned.
View Lorry Controller Status