- Craig A West brought us: libcurl now defaults to do CONNECT with HTTP

                                  Changelog

Daniel Stenberg (2 Feb 2009)

- Craig A West brought us: libcurl now defaults to do CONNECT with HTTP

  version 1.1 instead of 1.0 like before. This change also introduces the new

  proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to

  switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0

  option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0.

  I updated all test cases cases that use CONNECT and I tried to do some using

  --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run.

Daniel Stenberg (31 Jan 2009)

- When building with c-ares 1.6.1 (not yet released) or later and IPv6 support

  enabled, we can now take advantage of its brand new AF_UNSPEC support in

Curl and libcurl 7.19.4

 Public curl releases:         110

 Command line options:         131

 Command line options:         132

 curl_easy_setopt() options:   161

 Public functions in libcurl:  58

 Known libcurl bindings:       37

   the corresponding curl options --socks5-gssapi-service and

   --socks5-gssapi-nec

 o Improved IPv6 support when built with with c-ares >= 1.6.1

 o Added CURLPROXY_HTTP_1_0 and --proxy1.0

This release includes the following bugfixes:

        curl --noproxy localhost,get.this -x my-proxy:888 http://www.get.this/

 If the proxy is specified with --proxy1.0 instead of --proxy or -x, then

 curl will use HTTP/1.0 instead of HTTP/1.1 for any CONNECT attempts.

 curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5.

 See also the environment variables Curl support that offer further proxy

.IP "--proxy-ntlm"

Tells curl to use HTTP NTLM authentication when communicating with the given

proxy. Use \fI--ntlm\fP for enabling NTLM with a remote host.

.IP "--proxy1.0 <proxyhost[:port]>"

Use the specified HTTP 1.0 proxy. If the port number is not specified, it is

assumed at port 1080.

The only difference between this and the HTTP proxy option (\fI-x/--proxy\fP),

is that attempts to use CONNECT through the proxy will specify an HTTP 1.0

protocol instead of the default HTTP 1.1.

.IP "-p/--proxytunnel"

When an HTTP proxy is used (\fI-x/--proxy\fP), this option will cause non-HTTP

protocols to attempt to tunnel through the proxy instead of merely using it to

specified in the proxy string \fICURLOPT_PROXY\fP.

.IP CURLOPT_PROXYTYPE

Pass a long with this option to set type of the proxy. Available options for

this are \fICURLPROXY_HTTP\fP, \fICURLPROXY_SOCKS4\fP (added in 7.15.2),

\fICURLPROXY_SOCKS5\fP, \fICURLPROXY_SOCKS4A\fP (added in 7.18.0) and

\fICURLPROXY_SOCKS5_HOSTNAME\fP (added in 7.18.0). The HTTP type is

default. (Added in 7.10)

this are \fICURLPROXY_HTTP\fP, \fICURLPROXY_HTTP_1_0\fP (added in 7.19.4),

\fICURLPROXY_SOCKS4\fP (added in 7.15.2), \fICURLPROXY_SOCKS5\fP,

\fICURLPROXY_SOCKS4A\fP (added in 7.18.0) and \fICURLPROXY_SOCKS5_HOSTNAME\fP

(added in 7.18.0). The HTTP type is default. (Added in 7.10)

.IP CURLOPT_NOPROXY

Pass a pointer to a zero terminated string. The should be a comma- separated

list of hosts which do not use a proxy, if one is specified.  The only