Does libcurl support anonymous ftp server?

I'm using libcurl to download and upload files from Linux ftp server. Now the server supports anonymous users. However when I tried to upload a file to it, I always get the same error code 25 and error message Failed FTP upload: 553. I even tried the command curl and got the same error code. Cou

error when send email via curl

hello: when i send email through gmail is ok, but through mail.live failed. gmail: curl -n --ssl-reqd --mail-from "wang37...@gmail.com" --mail-rcpt "wang37...@live.com" --url smtp://smtp.gmail.com:465 -u wang37...@gmail.com -v --cacert cacert.pem it works. but send through live.mail, there has so

Re: Http Delete request return 400

On 7 November 2012 08:59, huancong deng wrote: > > 82 curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L); > 83 curl_easy_setopt(curl,CURLOPT_CUSTOMREQUEST,"delete"); Use "DELETE" and not "delete". -- Michael Wood --- Lis

Re: Using http DELETE how to add param

On Nov 6, 2012, at 8:55 PM, huancong deng wrote: > how can i use libcurl to sent a http delete request? Set CURLOPT_CUSTOMREQUEST to "DELETE" in your easy handle. > how can i add some to the http delete request?? What are you trying to accomplish? Nick Zitzmann

Using http DELETE how to add param

how can i use libcurl to sent a http delete rquest? how can i add some to the http delete request?? *Any help will be appreciated. Thanks in advance. * *:)* --- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette:

Re: [curl] Adding RFC2818 compliance to axTLS and moving helper functions to a generic place. (#46)

My personal clone at http://www.github.com/okoeroo/curl works clean across my hosts. I'll better make a clean pull request for easy integration. Daniel Stenberg schreef: >On Tue, 6 Nov 2012, Oscar Koeroo wrote: > >> Could you verify if I didn't mess up a bunch of text files? Like the >BUGS

Re: PATCH: gnutls: fix the error_is_fatal logic once and for all, hopefully (was: lib/gtls.c question about handshake())

On Tue, 6 Nov 2012, Alessandro Ghedini wrote: Looks like somenthing wrong in gnome-keyring [0], though I'm not sure what may have triggered it. Right. I'm a bit puzzled why GnuTLS unconditionally throws this at me, and I've asked them about this particular thing and I'll see where it ends.

Re: [curl] Adding RFC2818 compliance to axTLS and moving helper functions to a generic place. (#46)

On Tue, 6 Nov 2012, Oscar Koeroo wrote: Could you verify if I didn't mess up a bunch of text files? Like the BUGS file. I wasn't to careful with the push. Hm, the pull request 46 I still see there is 4 days old and doesn't apply cleanly. How do I find your updated work? -- / daniel.haxx.s

Re: PATCH: gnutls: fix the error_is_fatal logic once and for all, hopefully (was: lib/gtls.c question about handshake())

On mar, nov 06, 2012 at 07:29:22 +0100, Daniel Stenberg wrote: > On Wed, 24 Oct 2012, Alessandro Ghedini wrote: > > >I've rewritten the patch to fix the original broken logic, so that > >it now still prints "gnutls_handshake() warning: ..." and has the > >correct behaviour (i.e. doesn't break git)

Re: [curl] Adding RFC2818 compliance to axTLS and moving helper functions to a generic place. (#46)

On 06-11-12 19:50, Daniel Stenberg wrote: > On Mon, 5 Nov 2012, Oscar Koeroo wrote: > >>> As I already have a VERIFYHOST rework patch pending - basically what I >>> already shown before - do you think it makes sense for me to merge that >>> in first and then have your work rebased on top of that?

Re: "The Most Dangerous Code in the World"

On Mon, Oct 29, 2012 at 09:43:08PM +0100, Alessandro Ghedini wrote: > Anyway, I just run a quick grep on all the sources of the packages that build > depend on libcurl and those that explicitly set CURLOPT_SSL_VERIFYPEER are > very > few, even less those that set it to 1 (possibily 5-6). This said

Re: [curl] Adding RFC2818 compliance to axTLS and moving helper functions to a generic place. (#46)

On 06-11-12 19:50, Daniel Stenberg wrote: > On Mon, 5 Nov 2012, Oscar Koeroo wrote: > >>> As I already have a VERIFYHOST rework patch pending - basically what I >>> already shown before - do you think it makes sense for me to merge that >>> in first and then have your work rebased on top of that?

Re: [curl] Adding RFC2818 compliance to axTLS and moving helper functions to a generic place. (#46)

On Mon, 5 Nov 2012, Oscar Koeroo wrote: As I already have a VERIFYHOST rework patch pending - basically what I already shown before - do you think it makes sense for me to merge that in first and then have your work rebased on top of that? I'm fine with that. It depends a bit on how much chan

Re: PATCH: gnutls: fix the error_is_fatal logic once and for all, hopefully (was: lib/gtls.c question about handshake())

On Wed, 24 Oct 2012, Alessandro Ghedini wrote: I've rewritten the patch to fix the original broken logic, so that it now still prints "gnutls_handshake() warning: ..." and has the correct behaviour (i.e. doesn't break git). Thanks for this! Unfortunately I now have an annoying new problem -

Re: Custom http head free memory

On Tue, 6 Nov 2012, huancong deng wrote: when i use curl_slist_append to make my custom http head , must i free the memory like this? curl_slist_free_all(headers); /* free the header list */ Yes! i saw some example don't free the head

Re: Auth regression

On Mon, 5 Nov 2012, Nick Zitzmann wrote: If nobody objects, I'll merge this into master within shortly. I don't know if it re-introduces the original bug that the patch that caused the regression fixed or not, but I can verify that, at least when using the command line tool with the --anyaut