My first attempt did not include the TUNNEL option. When I did the original
test (without the TUNNEL option) I simply received a zero retrun code from
the PERFORM. My read callback routine was never invoked (thus nothing was
sent to the FTP site). This is why I tried the TUNNEL option. It was not
until I added the TUNNEL option that my read "callback" routine was
actually invoked by libcurl -- but then the return code indicated the write
error.

Any toughts on the zero return code but no data transfer?

----- Original Message -----
From: "Daniel Stenberg" <daniel_at_haxx.se>
To: "libcurl development" <curl-library_at_cool.haxx.se>
Sent: Wednesday, September 14, 2011 1:14 PM
Subject: Re: Failed Writing Body

> On Wed, 14 Sep 2011, Mark Schienbein wrote:
>
> > url="ftp.xxxxx.com"
> > upload-file="build.txt"
> > user="uuuser:pppasswd"
> > proxy="http://xxx.xxx.xxx.xxx:81
>
> These options will convert your operation into a HTTP PUT over the HTTP
proxy,
> and your proxy obviously is good enough to deal with that.
>
> > CRLOPT_PROXY
> > CRLOPT_PROXYTYPE (http1.1)
> > CRLOPT_PROXYPORT
> > CRLOPT_PROXYTTUNNEL
>
> These options will make a HTTP CONNECT "through" the proxy and then it'll
send
> the proper FTP commands to the remote server.
>
> These two requests are *vastly* different from each other. Using -v and
> CURLOPT_VERBOSE will reveal this.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-09-15