Loading CHANGES +3 −0 Original line number Diff line number Diff line Loading @@ -7,6 +7,9 @@ Changelog Daniel Stenberg (7 May 2009) - Man page *roff problems fixed thanks to input from Colin Watson. Problems reported in the Debian package. - Vijay G filed bug report #2723236 (http://curl.haxx.se/bug/view.cgi?id=2723236) identifying a problem with libcurl's TFTP code and its lack of dealing with the OACK packet. Loading RELEASE-NOTES +3 −1 Original line number Diff line number Diff line Loading @@ -41,6 +41,7 @@ This release includes the following bugfixes: o HTTP PUT protocol line endings portions mangled from CRLF to CRCRLF o Rejected SSL session ids are killed properly (for OpenSSL and GnuTLS builds) o Deal with the TFTP OACK packet o fixed roff mistakes in man pages This release includes the following known bugs: Loading @@ -53,6 +54,7 @@ advice from friends like these: Andre Guibert de Bruet, Andreas Farber, Frank Hempel, Pierre Brico, Kamil Dudka, Jim Freeman, Daniel Johnson, Toshio Kuratomi, Martin Storsjo, Pramod Sharma, Gisle Vanem, Leanic Lefever, Rainer Koenig, Sven Wegener, Tim Chen, Constantine Sapuntzakis, David McCreedy, Michael Smith Tim Chen, Constantine Sapuntzakis, David McCreedy, Michael Smith, Colin Watson Thanks! (and sorry if I forgot to mention someone) docs/libcurl/curl_easy_getinfo.3 +2 −2 Original line number Diff line number Diff line Loading @@ -209,7 +209,7 @@ this returns a 1 you know that the reason you didn't get data in return is because it didn't fulfill the condition. The long ths argument points to will get a zero stored if the condition instead was met. (Added in 7.19.4) .SH TIMES .NF .nf An overview of the six time values available from curl_easy_getinfo() curl_easy_perform() Loading @@ -221,7 +221,7 @@ curl_easy_perform() |--|--|--|--|--STARTTRANSFER |--|--|--|--|--|--TOTAL |--|--|--|--|--|--REDIRECT .FI .fi .IP NAMELOOKUP \fICURLINFO_NAMELOOKUP_TIME\fP. The time it took from the start until the name resolving was completed. Loading docs/libcurl/curl_easy_setopt.3 +2 −2 Original line number Diff line number Diff line Loading @@ -235,9 +235,9 @@ at the user's discretion. \fICURL_SOCKET_BAD\fP return value from the callback function will signal an unrecoverable error to the library and it will return \fICURLE_COULDNT_CONNECT\fP. This return code can be used for IP address blacklisting. The default behavior is: .Bd -literal -offset indent .nf return socket(addr->family, addr->socktype, addr->protocol); .Ed .fi (Option added in 7.17.1.) .IP CURLOPT_OPENSOCKETDATA Pass a pointer that will be untouched by libcurl and passed as the first Loading docs/libcurl/curl_multi_info_read.3 +2 −2 Original line number Diff line number Diff line Loading @@ -34,7 +34,7 @@ If more involved information is wanted, the particular "easy handle" in present in that struct and can thus be used in subsequent regular \fIcurl_easy_getinfo(3)\fP calls (or similar): .NF .nf struct CURLMsg { CURLMSG msg; /* what this message means */ CURL *easy_handle; /* the handle it concerns */ Loading @@ -43,7 +43,7 @@ present in that struct and can thus be used in subsequent regular CURLcode result; /* return code for transfer */ } data; }; .fi When \fBmsg\fP is \fICURLMSG_DONE\fP, the message identifies a transfer that is done, and then \fBresult\fP contains the return code for the easy handle that just completed. Loading Loading
CHANGES +3 −0 Original line number Diff line number Diff line Loading @@ -7,6 +7,9 @@ Changelog Daniel Stenberg (7 May 2009) - Man page *roff problems fixed thanks to input from Colin Watson. Problems reported in the Debian package. - Vijay G filed bug report #2723236 (http://curl.haxx.se/bug/view.cgi?id=2723236) identifying a problem with libcurl's TFTP code and its lack of dealing with the OACK packet. Loading
RELEASE-NOTES +3 −1 Original line number Diff line number Diff line Loading @@ -41,6 +41,7 @@ This release includes the following bugfixes: o HTTP PUT protocol line endings portions mangled from CRLF to CRCRLF o Rejected SSL session ids are killed properly (for OpenSSL and GnuTLS builds) o Deal with the TFTP OACK packet o fixed roff mistakes in man pages This release includes the following known bugs: Loading @@ -53,6 +54,7 @@ advice from friends like these: Andre Guibert de Bruet, Andreas Farber, Frank Hempel, Pierre Brico, Kamil Dudka, Jim Freeman, Daniel Johnson, Toshio Kuratomi, Martin Storsjo, Pramod Sharma, Gisle Vanem, Leanic Lefever, Rainer Koenig, Sven Wegener, Tim Chen, Constantine Sapuntzakis, David McCreedy, Michael Smith Tim Chen, Constantine Sapuntzakis, David McCreedy, Michael Smith, Colin Watson Thanks! (and sorry if I forgot to mention someone)
docs/libcurl/curl_easy_getinfo.3 +2 −2 Original line number Diff line number Diff line Loading @@ -209,7 +209,7 @@ this returns a 1 you know that the reason you didn't get data in return is because it didn't fulfill the condition. The long ths argument points to will get a zero stored if the condition instead was met. (Added in 7.19.4) .SH TIMES .NF .nf An overview of the six time values available from curl_easy_getinfo() curl_easy_perform() Loading @@ -221,7 +221,7 @@ curl_easy_perform() |--|--|--|--|--STARTTRANSFER |--|--|--|--|--|--TOTAL |--|--|--|--|--|--REDIRECT .FI .fi .IP NAMELOOKUP \fICURLINFO_NAMELOOKUP_TIME\fP. The time it took from the start until the name resolving was completed. Loading
docs/libcurl/curl_easy_setopt.3 +2 −2 Original line number Diff line number Diff line Loading @@ -235,9 +235,9 @@ at the user's discretion. \fICURL_SOCKET_BAD\fP return value from the callback function will signal an unrecoverable error to the library and it will return \fICURLE_COULDNT_CONNECT\fP. This return code can be used for IP address blacklisting. The default behavior is: .Bd -literal -offset indent .nf return socket(addr->family, addr->socktype, addr->protocol); .Ed .fi (Option added in 7.17.1.) .IP CURLOPT_OPENSOCKETDATA Pass a pointer that will be untouched by libcurl and passed as the first Loading
docs/libcurl/curl_multi_info_read.3 +2 −2 Original line number Diff line number Diff line Loading @@ -34,7 +34,7 @@ If more involved information is wanted, the particular "easy handle" in present in that struct and can thus be used in subsequent regular \fIcurl_easy_getinfo(3)\fP calls (or similar): .NF .nf struct CURLMsg { CURLMSG msg; /* what this message means */ CURL *easy_handle; /* the handle it concerns */ Loading @@ -43,7 +43,7 @@ present in that struct and can thus be used in subsequent regular CURLcode result; /* return code for transfer */ } data; }; .fi When \fBmsg\fP is \fICURLMSG_DONE\fP, the message identifies a transfer that is done, and then \fBresult\fP contains the return code for the easy handle that just completed. Loading