LibCurlNet problem reusing easy handle

2012-05-21 Thread Lukasz Buczkowski
Hi, Thanks for great library! I'm having some trouble reusing easy handle. What I do. 1) setup connection to use ssl 2) start first transfer it returns ok 3) next transfer returns CURLE_FTP_WRITE_ERROR Additional info. When I read debug information I find following message: 522 SSL connection

Winbuild IPv6 support always disabled in libcurl 7.25.0

2012-05-21 Thread Jan Ehrhardt
I tried to update php_curl.dll to libcurl 7.25.0, but discovered that IPv6 support was enabled (no matter what options I chose). At last, I discovered why. This patch was incomplete: https://github.com/bagder/curl/commit/575f3c30ed60aafddbaeeb26745cca942fb9ee2f I commented the patch, but do

Re: [PATCH] add CURLINFO_SSL_VERIFYRESULT_STR providing a human-readable error string

2012-05-21 Thread Kamil Dudka
On Monday 14 May 2012 17:31:37 Dan Fandrich wrote: On Mon, May 14, 2012 at 04:48:48PM +0200, Kamil Dudka wrote: Although I missed the devel freeze for 7.25.1, I am sending an up2date version of the patch to keep this thread alive. If anybody could comment on the patch meanwhile, it would

CURLOPT_URL always lists

2012-05-21 Thread Anders Havn
Hi, I'm just wondering if I'm doing something wrong or this is just how it works. I always set CURLOPT_URL to my base url, but then it also always lists the files and folders in the base url. This is how my codes looks when I delete a file: NSString username = @username; NSString password =

Re: CURLOPT_URL always lists

2012-05-21 Thread Dan Fandrich
On Mon, May 21, 2012 at 06:47:55PM +0200, Anders Havn wrote: I'm just wondering if I'm doing something wrong or this is just how it works. I always set CURLOPT_URL to my base url, but then it also always lists the files and folders in the base url. curl will always transfer a file unless

RE: SMTP: multi interface produce wrong error code for unknown recipient

2012-05-21 Thread Steve Holme
Hi Gokhan, I just noticed a small flaw in SMTP when it is used with multi interface. If the recipient is unknown by the SMTP server, libcurl ends up with error code CURLE_RECV_ERROR instead of a more meaningful one like CURLE_LOGIN_DENIED (which is provided with easy interface currently). I

RE: SMTP: multi interface produce wrong error code for unknown recipient

2012-05-21 Thread Daniel Stenberg
On Mon, 21 May 2012, Steve Holme wrote: Can anyone who is more familiar with the multi interface tell us if smtp_done() is intentionally called even when there is a failure? Yes it is and it will. See lib/url.c:Curl_done() at around line 5378. It will however get the status code and

RE: SMTP: multi interface produce wrong error code for unknown recipient

2012-05-21 Thread Steve Holme
Hi Daniel, Can anyone who is more familiar with the multi interface tell us if smtp_done() is intentionally called even when there is a failure? Yes it is and it will. See lib/url.c:Curl_done() at around line 5378. It will however get the status code and premature state passed in as