LibCurl source version:7.15 platform -windows xp servicepack 2 Please find the details libcurl log, inside of Curl_perform method of tranfer.c file I added few log message for help.
009-03-19 13:02:45 I #3648 naInet DoFtpDownload start 2009-03-19 13:02:45 I #3648 naInet Trying to find an usable proxy using IE settings 2009-03-19 13:02:45 I #3648 naInet Found proxy server with IE settings : 172.16.220.184 2009-03-19 13:02:45 I #3648 naInet m_bUseAuthentication 2009-03-19 13:02:45 I #3648 naInet m_bUseProxyAuthentication 2009-03-19 13:02:45 I #3648 naInet Calling curl_easy_perform from doftpdownload 2009-03-19 13:02:45 X #3648 naInet Info:Start curl_easy_perform 2009-03-19 13:02:45 X #3648 naInet Info:calling Curl_perform 2009-03-19 13:02:45 X #3648 naInet Info:start Curl_perform 2009-03-19 13:02:45 X #3648 naInet Info:About to connect() to proxy 172.16.220.184 port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info: Trying 172.16.220.184... 2009-03-19 13:02:45 X #3648 naInet Info:connected 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Connected to 172.16.220.184 (172.16.220.184) port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called connect_host return code:0 2009-03-19 13:02:45 X #3648 naInet => Send header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_retry_request return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Closing connection #0 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_done return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Issue another request to this URL: 'ftp://172.16.220.151:21/SiteStat.xml' 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_follow return code:0 2009-03-19 13:02:45 X #3648 naInet Info:About to connect() to proxy 172.16.220.184 port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info: Trying 172.16.220.184... 2009-03-19 13:02:45 X #3648 naInet Info:connected 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Connected to 172.16.220.184 (172.16.220.184) port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called connect_host return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Proxy auth using NTLM with user 'josy' 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet => Send header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_retry_request return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Closing connection #0 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_done return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Issue another request to this URL: 'ftp://172.16.220.151:21/SiteStat.xml' 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_follow return code:0 2009-03-19 13:02:45 X #3648 naInet Info:About to connect() to proxy 172.16.220.184 port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info: Trying 172.16.220.184... 2009-03-19 13:02:45 X #3648 naInet Info:connected 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Connected to 172.16.220.184 (172.16.220.184) port 8080 (#0) 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called connect_host return code:0 2009-03-19 13:02:45 X #3648 naInet => Send header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet <= Recv header 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_retry_request return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Closing connection #0 2009-03-19 13:02:45 X #3648 naInet 2009-03-19 13:02:45 X #3648 naInet Info:Curl_perform::Called Curl_done return code:0 2009-03-19 13:02:45 X #3648 naInet Info:Issue another request to this URL: 'ftp://172.16.220.151:21/SiteStat.xml' Message: 4 Date: Wed, 18 Mar 2009 13:14:51 +0100 (CET) From: Daniel Stenberg <[email protected]> Subject: Re: help To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII On Tue, 17 Mar 2009, [email protected] wrote: > We want to download a file from FTP server, proxy used is ISA 2006, > and the proxy authentication used is NTLM. > If Authentication is failed due to wrong user id. Curl is trying to > connect more than 100 times to the FTP repository server using proxy. If you told libcurl to use the proxy, libcurl will only access the proxy and not the FTP server at all so I don't see how this is libcurl doing the retries. libcurl should not retry bad authentication cases at all. But the logs look curious - does the proxy somehow redirect the client to the FTP site? Can you show us more detailed protocol logs from this? And do tell us what libcurl version on what platform you're running. -- / daniel.haxx.se ------------------------------ Message: 5 Date: Wed, 18 Mar 2009 13:48:59 +0100 (CET) From: Daniel Stenberg <[email protected]> Subject: Re: [PATCH] nss: enable new AES TLS ciphersuites To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 18 Mar 2009, Kamil Dudka wrote: > There is no reason to not use them in nss-enabled libcurl as these > ciphers are commonly used when OpenSSL support is compiled in. The > attached patch enables these ciphers explicitly. Thanks, applied! -- / daniel.haxx.se ------------------------------ Message: 6 Date: Wed, 18 Mar 2009 14:04:31 +0100 (CET) From: Daniel Stenberg <[email protected]> Subject: SCP and SFTP tests? To: libcurl hacking <[email protected]> Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Hey friends, Over in the libssh2 camp, there have been some pretty drastic speed improvements recently (4-10 times faster transfers than libssh2 1.0 have been measured) and as I know a lot of you use libssh2 for powering the SCP and SFTP transfers libcurl can do, I figure it could be a good idea to mention this here! I would love to get some further testing of the current CVS version of libssh2 so that we can release a 1.1 in a few days with greater confidence. If CVS isn't for you, get a daily snapshot from here: http://daniel.haxx.se/projects/libssh2/snapshots.html And to read some of my blurb about the actual performance work, go here: http://daniel.haxx.se/blog/2009/03/16/libssh2-upped-a-notch/ And please take any problems, reports or cheering to the libssh2-devel list! -- / daniel.haxx.se ------------------------------ Message: 7 Date: Wed, 18 Mar 2009 08:16:15 -0500 From: Jeff Pohlmeyer <[email protected]> Subject: Re: Effective URL different if CURLOPT_NOBODY is set to true To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Mar 18, 2009, [email protected] wrote: > ...using CURLOPT_HEADERFUNCTION > ...when (size*nmemb)==2 > ...abort the transfer. Err, that is not quite right, sorry. You should only cancel the transfer after a set of headers that *does not* contain a location header. That gets a bit more complicated, maybe it's easier to explain with an example: /***************/ #include <string.h> #include <stdio.h> #include <curl/curl.h> #define TRUE 1 #define FALSE 0 static int following=FALSE; /* Our header callback */ size_t hdr_cb( void *hdr, size_t size, size_t nmemb, void *unused) { size_t rv=size*nmemb; if (rv==2) { /* The end of this set of headers */ if (following) { /* If we are following, reset the flag and carry on */ following=FALSE; } else { /* Cancel the transfer */ return 0; } } else { /* Check to see if we should keep going */ if (strncasecmp(hdr, "Location:",9)==0) { following=TRUE; } } return rv; } int main(int argc, char*argv[]) { CURL*curl=curl_easy_init(); curl_easy_setopt(curl,CURLOPT_URL,argv[1]); curl_easy_setopt(curl,CURLOPT_HEADERFUNCTION,hdr_cb); curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1); CURLcode rv=curl_easy_perform(curl); char*eff_url=NULL; curl_easy_getinfo(curl, CURLINFO_EFFECTIVE_URL, &eff_url); printf("%s\n", eff_url); curl_easy_cleanup(curl); return rv==CURLE_WRITE_ERROR?0:rv; } /***************/ It would actually be simpler to use a CURLOPT_WRITEFUNCTION and abort on the very first chunk of data it receives, but that would require downloading a few extra bytes each time. - Jeff ------------------------------ Message: 8 Date: Wed, 18 Mar 2009 14:37:31 +0000 From: Emily Mark <[email protected]> Subject: SSL Support Other than OpenSSL? To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Hi, I just wondered if there are any alternatives to OpenSSL for cURL? Has anyone developed something different? Thanks, Emily _________________________________________________________________ Reunite with the people closest to you, chat face to face with Messenger. http://go.microsoft.com/?linkid=9650736 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://cool.haxx.se/pipermail/curl-library/attachments/20090318/4c6d97bf/attachment-0001.htm> ------------------------------ Message: 9 Date: Wed, 18 Mar 2009 17:02:02 +0200 From: Michael Wood <[email protected]> Subject: Re: SSL Support Other than OpenSSL? To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Wed, Mar 18, 2009 at 4:37 PM, Emily Mark <[email protected]> wrote: > Hi, > > I just wondered if there are any alternatives to OpenSSL for cURL? Has > anyone developed something different? Yes, see http://curl.haxx.se/docs/features.html and http://curl.haxx.se/docs/install.html says: curl can be built to use a whole range of libraries to provide various useful services, and configure will try to auto-detect a decent default. But if you want to alter it, you can select how to deal with each individual library. To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that you need to use both --without-ssl and --with-gnutls. To build with yassl support instead of OpenSSL or GnuTLS, you must build yassl with its OpenSSL emulation enabled and point to that directory root with configure --with-ssl. To build with NSS support instead of OpenSSL for SSL/TLS, note that you need to use both --without-ssl and --with-nss. -- Michael Wood <[email protected]> ------------------------------ Message: 10 Date: Wed, 18 Mar 2009 18:41:46 +0100 From: Piotr Dobrogost <[email protected]> Subject: Re: SSL Support Other than OpenSSL? To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Michael Wood wrote: > On Wed, Mar 18, 2009 at 4:37 PM, Emily Mark <[email protected]> wrote: >> Hi, >> >> I just wondered if there are any alternatives to OpenSSL for cURL? >> Has anyone developed something different? > > Yes, see http://curl.haxx.se/docs/features.html > > and http://curl.haxx.se/docs/install.html says: > > To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that > you need to use both --without-ssl and --with-gnutls. > > To build with yassl support instead of OpenSSL or GnuTLS, you must build > yassl with its OpenSSL emulation enabled and point to that directory root > with configure --with-ssl. > > To build with NSS support instead of OpenSSL for SSL/TLS, note that > you need to use both --without-ssl and --with-nss. I take it from the above excerpt that naming of ssl parameters in libcurl's build script is misleading at least. It looks like --with-ssl refers only to OpenSSL. Shouldn't it then be called -with-openssl instead? This way one wouldn't have to give --without-ssl with other SSL libs. Piotr Dobrogost ------------------------------ Message: 11 Date: Wed, 18 Mar 2009 19:36:04 +0100 (CET) From: Daniel Stenberg <[email protected]> Subject: Re: SSL Support Other than OpenSSL? To: libcurl development <[email protected]> Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 18 Mar 2009, Piotr Dobrogost wrote: > I take it from the above excerpt that naming of ssl parameters in > libcurl's build script is misleading at least. It looks like > --with-ssl refers only to OpenSSL. Shouldn't it then be called > -with-openssl instead? This way one wouldn't have to give --without-ssl with > other SSL libs. I would rather have it test for each different lib, one by one and pick the first one that works. And then we could add an --with-openssl for explictly asking for OpenSSL. -- / daniel.haxx.se ------------------------------ _______________________________________________ curl-library mailing list [email protected] http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library End of curl-library Digest, Vol 43, Issue 25 ********************************************
