2
Patrick M (15 October 2007)
3
- Fixed the dynamic CURLOPT_POSTFIELDS problem: this option is now static again
4
and option CURLOPT_COPYPOSTFIELDS has been added to support dynamic mode.
7
Daniel S (5 October 2007)
8
- Michael Wallner made the CULROPT_COOKIELIST option support a new magic
9
string: "FLUSH". Using that will cause libcurl to flush its cookies to the
10
CURLOPT_COOKIEJAR file.
11
S�lo documentaci�n HECHO
13
Daniel S (3 October 2007)
14
- Alexey Pesternikov introduced CURLOPT_OPENSOCKETFUNCTION and
15
CURLOPT_OPENSOCKETDATA to set a callback that allows an application to
16
replace the socket() call used by libcurl. It basically allows the app to
17
change address, protocol or whatever of the socket.
20
- I renamed the CURLE_SSL_PEER_CERTIFICATE error code to
21
CURLE_PEER_FAILED_VERIFICATION (standard CURL_NO_OLDIES style), and made
22
this return code get used by the previous SSH MD5 fingerprint check in case
26
- Based on a patch brought by Johnny Luong, libcurl now offers
27
CURLOPT_SSH_HOST_PUBLIC_KEY_MD5 and the curl tool --hostpubmd5. They both
28
make the SCP or SFTP connection verify the remote host's md5 checksum of the
29
public key before doing a connect, to reduce the risk of a man-in-the-middle
33
Daniel S (26 September 2007)
34
- Philip Langdale provided the new CURLOPT_POST301 option for
35
curl_easy_setopt() that alters how libcurl functions when following
36
redirects. It makes libcurl obey the RFC2616 when a 301 response is received
37
after a non-GET request is made. Default libcurl behaviour is to change
38
method to GET in the subsequent request (like it does for response code 302
39
- because that's what many/most browsers do), but with this CURLOPT_POST301
40
option enabled it will do what the spec says and do the next request using
41
the same method again. I.e keep POST after 301.
43
The curl tool got this option as --post301
45
Test case 1011 and 1012 were added to verify.
48
- Renamed the curl_ftpssl enum to curl_usessl and its enumerated constants,
49
creating macros for backward compatibility:
51
CURLFTPSSL_NONE => CURLUSESSL_NONE
52
CURLFTPSSL_TRY => CURLUSESSL_TRY
53
CURLFTPSSL_CONTROL => CURLUSESSL_CONTROL
54
CURLFTPSSL_ALL => CURLUSESSL_ALL
55
CURLFTPSSL_LAST => CURLUSESSL_LAST
58
- Renamed several libcurl error codes and options to make them more general
59
and allow reuse by multiple protocols. Several unused error codes were
60
removed. In all cases, macros were added to preserve source (and binary)
61
compatibility with the old names. These macros are subject to removal at
62
a future date, but probably not before 2009. An application can be
63
tested to see if it is using any obsolete code by compiling it with the
64
CURL_NO_OLDIES macro defined.
66
The following unused error codes were removed:
68
CURLE_BAD_CALLING_ORDER
69
CURLE_BAD_PASSWORD_ENTERED
70
CURLE_FTP_CANT_RECONNECT
71
CURLE_FTP_COULDNT_GET_SIZE
72
CURLE_FTP_COULDNT_SET_ASCII
73
CURLE_FTP_USER_PASSWORD_INCORRECT
74
CURLE_FTP_WEIRD_USER_REPLY
76
CURLE_LIBRARY_NOT_FOUND
80
CURLE_URL_MALFORMAT_USER
81
EFECTIVAMENTE NO SE USAN
82
The following error codes were renamed:
84
CURLE_FTP_ACCESS_DENIED => CURLE_REMOTE_ACCESS_DENIED
85
CURLE_FTP_COULDNT_SET_BINARY => CURLE_FTP_COULDNT_SET_TYPE
86
CURLE_FTP_SSL_FAILED => CURLE_USE_SSL_FAILED
87
CURLE_FTP_QUOTE_ERROR => CURLE_QUOTE_ERROR
88
CURLE_TFTP_DISKFULL => CURLE_REMOTE_DISK_FULL
89
CURLE_TFTP_EXISTS => CURLE_REMOTE_FILE_EXISTS
90
CURLE_HTTP_RANGE_ERROR => CURLE_RANGE_ERROR
91
NO LOS USO EXPLICITAMENTE
92
The following options were renamed:
94
CURLOPT_SSLKEYPASSWD => CURLOPT_KEYPASSWD
95
CURLOPT_FTPAPPEND => CURLOPT_APPEND
96
CURLOPT_FTPLISTONLY => CURLOPT_DIRLISTONLY
97
CURLOPT_FTP_SSL => CURLOPT_USE_SSL
101
A few more changes will take place with the next SONAME bump of the
102
library. These are documented in docs/TODO
104
- Documented some newer error codes in libcurl-error(3)
106
- Added more accurate error code returns from SFTP operations. Added test
107
case 615 to test an SFTP upload failure.
109
- Patrick Monnerat and I modified libcurl so that now it *copies* all strings
110
passed to it with curl_easy_setopt()! Previously it has always just refered
111
to the data, forcing the user to keep the data around until libcurl is done
112
with it. That is now history and libcurl will instead clone the given
113
strings and keep private copies. This is also part of Patrick Monnerat's
116
Due to this being a somewhat interesting change API wise, I've decided to
117
bump the version of the upcoming release to 7.17.0. Older applications will
118
of course not notice this change nor do they have to care, but new
119
applications can be written to take advantage of this.
added
removed
CHANGES
