On Tue, 22 May 2007, Gerry Patterson wrote:

> here is one example that I tried:
>
> curl --proxy-ntlm webproxy.foo.bar.com:8080 \
> --proxy-user scott:tiger \
> --user silly.msname.com.au\\foo:Cq5qXmg882 \
> --output test.xls \
> --cert-type DER \
> --cert /apps/cert/ABtrust.der:Cq5qXmg882 \
> 'https://silly.msname.com.au/scripts/IsapiDownload.dll?w=ETPS&filename=%5CMailing%5FHouse%5Cfoo%5Cdownload%5CTLS%2DWeekending180507%2Ezip'
>
> Most of the attempts returned:
>
> curl: (7) couldn't connect to host

This means curl couldn't connect TCP-wise to a given host. The reason is
because --proxy-ntlm takes no additional argument so curl treats your command
line as having two URLs.

You want --proxy [host:port] to specify the proxy, and --proxy-ntlm to enable
NTLM auth for the given proxy.

Also, your cert usage is probably not correct if all you want to do is verify
the peer's certificate, as --cert and --cert-type is for client certs. You
rather want no option at all to use the default ca-cert check, or
--cacert/--capath to specify where your custom ca cert bundle is.

Or use -k to skip the check of the peer's true identity.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html