Age | Commit message (Collapse) | Author |
|
the new format but there's still much more to be said and done
|
|
|
|
new ones. Many more of the old ones must be "ported" to this new format
to make the test suite complete again.
|
|
|
|
|
|
|
|
|
|
afterwards (bug #426442)
|
|
|
|
|
|
|
|
into the DOS kind!
|
|
|
|
about the libcurl SSL status)
|
|
properly! (?) Anyone has any better solution then please step forward!
|
|
|
|
|
|
is a FTPS connection as the data transfer is then done unencrypted!
|
|
to
|
|
|
|
|
|
|
|
other libs
|
|
|
|
symbol, but libcurl will not return this ever
|
|
5.2 "How can I receive all data into a large memory chunk?"
|
|
|
|
|
|
chunk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ssl peer verify fixes and more
|
|
CURLE_SSL_PEER_CERTIFICATE is added
|
|
|
|
code for peer certificate errors
|
|
|
|
|
|
|
|
already been transfered no longer returns error but instead is OK. The
reasoning behind this is of course that no extra actions need to be taken
and it is as if a transfer had been successfully performed.
|
|
strnequal() approach that really didn't follow the RFC properly
|
|
|
|
|
|
|