CURLE_BAD_FUNCTION_ARGUMENT when setting CURLOPT_POSTFIELDSIZE to -1

2017-10-31 Thread Andrew Lambert
Hello, I just downloaded 7.56.1 and discovered that setting CURLOPT_POSTFIELDSIZE to -1 returns CURLE_BAD_FUNCTION_ARGUMENT. Was this intentional? From change message it looks like it might have been changed by accident:

Re: Should curl package maintainers enable libidn2 by default or no?

2017-10-31 Thread Daniel Stenberg
On Tue, 31 Oct 2017, Ryan Schmidt wrote: Today's curl (7.56.1) automatically enables the use of libidn2, unless explicitly disabled via the --without-libidn2 configure flag. Do I take this to mean that curl with libidn2 is not considered dangerous anymore, and that it is now recommended for

Should curl package maintainers enable libidn2 by default or no?

2017-10-31 Thread Ryan Schmidt
Hi, I maintain curl in MacPorts. We used to build curl with libidn 1.x support enabled all the time. We stopped doing that when the curl version was 7.43.0 in June 2015 in response to this post from Daniel which said doing so represented a security vulnerability:

Re: Semantics of CURLINFO_SIZE_DOWNLOAD_T

2017-10-31 Thread Daniel Stenberg
On Tue, 31 Oct 2017, Johan Gill via curl-library wrote: Quoting the documentation for CURLINFO_SIZE_DOWNLOAD_T: "The amount is only for the latest transfer and will be reset again for each new transfer." What does that mean when one uses the multi interface, and has a loop with

Re: Adding QUIC support to curl

2017-10-31 Thread Dmitri Tikhonov
On Tue, Oct 31, 2017 at 09:22:39AM +, Lucas Pardue via curl-library wrote: > Some nice discussion going on, just wanted to bump the visibility of > the curl QUIC wiki page. There's some topics that could be enhanced > with information if the work is to begin. It might also be nice to > capture

Re: Adding QUIC support to curl

2017-10-31 Thread Dmitri Tikhonov
On Mon, Oct 30, 2017 at 10:55:06PM -0400, Dmitri Tikhonov wrote: > On Mon, Oct 30, 2017 at 10:39:14PM +0100, Daniel Stenberg wrote: > > but I too don't have a lot of extra to bring to the table on this > > right now for me it is primarily because I haven't properly read up > > on how the lsquic

Re: Adding QUIC support to curl

2017-10-31 Thread Dmitri Tikhonov
On Tue, Oct 31, 2017 at 12:42:44PM +0100, Gisle Vanem via curl-library wrote: > Lucas Pardue wrote: > > > >Whoops, the page is located at https://github.com/curl/curl/wiki/QUIC. > > That lists: > ngtcp2 (C-library) > MozQuic (C++ library) > quicly (C-library) > LiteSpeed QUIC client

Re: Adding QUIC support to curl

2017-10-31 Thread Gisle Vanem via curl-library
Lucas Pardue wrote: Some nice discussion going on, just wanted to bump the visibility of the curl QUIC wiki page. Whoops, the page is located at https://github.com/curl/curl/wiki/QUIC. That lists: ngtcp2 (C-library) MozQuic (C++ library) quicly (C-library) LiteSpeed QUIC client

Re: Adding QUIC support to curl

2017-10-31 Thread James Fuller
thx for the link (was just about to ask...) , J On 31 October 2017 at 10:29, Lucas Pardue via curl-library wrote: >> Some nice discussion going on, just wanted to bump the visibility of the curl >> QUIC wiki page. > > Whoops, the page is located at

RE: Adding QUIC support to curl

2017-10-31 Thread Lucas Pardue via curl-library
> Some nice discussion going on, just wanted to bump the visibility of the curl > QUIC wiki page. Whoops, the page is located at https://github.com/curl/curl/wiki/QUIC. Lucas --- Unsubscribe:

RE: Adding QUIC support to curl

2017-10-31 Thread Lucas Pardue via curl-library
Hi Dmitri, > > Thanks for bringing this topic to the table. I'm really keen on seeing some > movement in this area and I'm thrilled to see you here pulling strings to make > things happen. I'll do my best to aid this effort! > > Some nice discussion going on, just wanted to bump the visibility