Age | Commit message (Collapse) | Author |
|
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.
|
|
is an inofficial PROXY4 variant that sends the hostname to the proxy instead
of the resolved address (which is already supported by SOCKS5). --socks4a is
the curl command line option for it and CURLOPT_PROXYTYPE can now be set to
CURLPROXY_SOCKS4A as well.
|
|
|
|
|
|
function but without a return statement. While fixing that, I also took care
about adding some better comments for the generated code.
|
|
|
|
(http://curl.haxx.se/mail/lib-2007-12/0252.html) in detect_proxy() which
failed to set the bits.proxy variable properly when an environment variable
told libcurl to use a http proxy.
|
|
(http://curl.haxx.se/bug/view.cgi?id=1850730) I wrote up test case 552. The
test is doing a 70K POST with a read callback and an ioctl callback over a
proxy requiring Digest auth. The test case code is more or less identical to
the test recipe code provided by Spacen Jasset (who submitted the bug report).
|
|
|
|
|
|
(http://curl.haxx.se/bug/view.cgi?id=1856628) and provided a fix for the
(small) memory leak in the SSL session ID caching code. It happened when a
previous entry in the cache was re-used.
|
|
components doesn't have read permission set.
|
|
directory components doesn't have read permission set.
|
|
--manual text.
|
|
a file truncation problem on Windows build targets triggered when retrying
a download with curl.
|
|
and makes wrong asumptions of build target when it isn't specified. So,
if no build target has been defined we will target WinXP when building
with MSVC 9.0 (VS2008).
|
|
|
|
defines in the SDK somehow differently so we have to add a define to the
config-win32.h file to make select.h compile nicely.
|
|
|
|
A failed attempt to repeat bug report #1850730 (ie the test works fine).
|
|
|
|
will prompt for a password. Denis Bredelet pointed out!
|
|
|
|
|
|
|
|
(http://curl.haxx.se/bug/view.cgi?id=1849764) with an included fix. He
identified a problem for re-used connections that previously had sent
Expect: 100-continue and in some situations the subsequent POST (that didn't
use Expect:) still had the internal flag set for its use. David's fix (that
makes the setting of the flag in every single request unconditionally) is
fine and is now used!
|
|
added the --no-keep-alive option that can disable that on demand.
|
|
values and what they mean
|
|
|
|
|