| Age | Commit message (Collapse) | Author |
|---|
|
already worked for FTP:// URLs
|
|
spanking new CURLOPT_SEEKFUNCTION simply to take advantage of the improved
performance for the upload resume cases where you want to upload the last
few bytes of a very large file. To implement this decently, I had to switch
the client code for uploading from fopen()/fread() to plain open()/read() so
that we can use lseek() to do >32bit seeks (as fseek() doesn't allow that)
on systems that offer support for that.
|
|
(it already before skipped /usr/lib). /usr/lib64 is the default library
directory on many 64bit systems and it's unlikely that anyone would use the
path privately on systems where it's not.
|
|
|
|
109 - curl_easy_pause
110 - seekfunction
|
|
libcurl to seek in a given input stream. This is particularly important when
doing upload resumes when there's already a huge part of the file present
remotely. Before, and still if this callback isn't used, libcurl will read
and through away the entire file up to the point to where the resuming
begins (which of course can be a slow opereration depending on file size,
I/O bandwidth and more). This new function will also be preferred to get
used instead of the CURLOPT_IOCTLFUNCTION for seeking back in a stream when
doing multi-stage HTTP auth with POST/PUT.
|
|
(http://curl.haxx.se/bug/view.cgi?id=1868255) with a patch. It identifies
and fixes a problem with parsing WWW-Authenticate: headers with additional
spaces in the line that the parser wasn't written to deal with.
|
|
|
|
|
|
|
|
locations search list.
|
|
|
|
new minimum SSH version support for SCP, SFTP and SOCKS tests.
Some verbosity which still remains, will go out before next release.
|
|
authentication failures when using OpenSSH 2.9.9 or SunSSH.
Verified fact: Even when only using publickey authentication,
OpenSSH and SunSSH first validate the user, this implies that
if the user validation fails, 'invalid user', the publickey
authentication will not be allowed to complete.
|
|
and the write callbacks that now can make a connection's reading and/or
writing get paused.
|
|
|
|
http://cool.haxx.se/cvs.cgi/curl/include/curl/curl.h.diff?r1=1.336&r2=1.337
|
|
failures when using OpenSSH 2.9.9 or SunSSH
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
added: 117 - Eric Landes patch for introducing the --tcp-keep* options
|
|
(http://curl.haxx.se/bug/view.cgi?id=1863171) where he pointed out that
libcurl's date parser didn't accept a +1300 time zone which actually is used
fairly often (like New Zealand's Dailight Savings Time), so I modified the
parser to now accept up to and including -1400 to +1400.
|
|
|
|
code to instead introduce support for a new proxy type called
CURLPROXY_SOCKS5_HOSTNAME that is used to send the host name to the proxy
instead of IP address and there's thus no longer any need for a new
curl_easy_setopt() option.
The default SOCKS5 proxy is again back to sending the IP address to the
proxy. The new curl command line option for enabling sending host name to a
SOCKS5 proxy is now --socks5-hostname.
|
|
|
|
|
|
fails, just issue a warning and ignore the failure.
|
|
|
|
added 116 - bug #1863171, curl_getdate() bug
|
|
|
|
proxy do the host name resolving and only if --socks5ip (or
CURLOPT_SOCKS5_RESOLVE_LOCAL) is used we resolve the host name locally and
pass on the IP address only to the proxy.
|
|
(for next SONAME bump)
|
|
|
|
|
|
later to accept 'none' as an indication to disable connection multiplexing
|
|
ConnectTimeout
ForwardX11Trusted
HashKnownHosts
RekeyLimit
ServerAliveCountMax
ServerAliveInterval
|
|
- Capability of running socks5 tests must be based on ssh daemon version
and not on ssh client version.
|
|
|
|
requires a non blank argument.
|
|
SCP, SFTP and SOCKS4 tests is now OpenSSH 2.9.9 or SunSSH 1.0
For SOCKS5 tests minimum versions are OpenSSH 3.7 or SunSSH 1.0
|
|
Use TRUE/FALSE from setup_once.h.
|
|
|
|
decoding where a write error (or abort return from a callback) didn't stop
libcurl's processing.
|
|
made it an unsigned int. The type was only used in the curl_sockaddr struct
definition (only used by the curl_opensocket_callback). On all platforms I
could find information about, socklen_t is 32 unsigned bits large so I don't
think this will break the API or ABI. The main reason for this change is of
course for all the platforms that don't have a socklen_t definition in their
headers to build fine again. Providing our own configure magic and custom
definition of socklen_t on those systems proved to work but was a lot of
cruft, code and extra magic needed - when this very small change of type seems
harmless and still solves the missing socklen_t problem.
|
