Re: Difference in libcurl dependencies between 7.41 and 7.57

2018-04-25 Thread Daniel Stenberg
On Thu, 26 Apr 2018, belussi1988 wrote: For a very long time I was using in my system libcurl version 7.41 which was depended on the following 3rd party libs: readelf -a /usr/lib/libcurl.so | grep NEEDED 0x0001 (NEEDED) Shared library: [libssl.so.1.0.0] 0x0001 (NEEDED) Shared library: [

Difference in libcurl dependencies between 7.41 and 7.57

2018-04-25 Thread belussi1988
Hi, For a very long time I was using in my system libcurl version 7.41 which was depended on the following 3rd party libs: readelf -a /usr/lib/libcurl.so | grep NEEDED 0x0001 (NEEDED) Shared library: [libssl.so.1.0.0] 0x0001 (NEEDED) Shared library: [libcrypto.so.1.0.0] 0x0001 (NEEDE

Re: encoding expectations

2018-04-25 Thread Michael Kilburn
On Tue, 24 Apr 2018, Daniel Stenberg wrote: > I would have said unconditionally yes, but then your comment about winidn made > me look that up and yes that seems to require that the host name is provided > as UTF-8 for it to work! I find that a little odd, but I can live with it. Probably becaus

Re: Uncompress HTTP responses if no Accept-Encoding was sent?

2018-04-25 Thread Daniel Stenberg
On Wed, 25 Apr 2018, Rainer Canavan wrote: I would conclude that libcurl should still try to decompress a response with a supported Content-Encoding, however Curl_http_readwrite_headers() explicitly checks if data->set.str[STRING_ENCODING] was set (i.e. an Accept-Encoding header was sent), and t

Re: Uncompress HTTP responses if no Accept-Encoding was sent?

2018-04-25 Thread Dmitri Tikhonov
On Wed, Apr 25, 2018 at 01:10:17PM +0200, Rainer Canavan wrote: > Curl_http_readwrite_headers() explicitly checks if > data->set.str[STRING_ENCODING] was set (i.e. an Accept-Encoding header > was sent), and therefore disables compression. > > I would simply remove that check for STRING_ENCODING. O

Uncompress HTTP responses if no Accept-Encoding was sent?

2018-04-25 Thread Rainer Canavan
Regarding the handling of the Accept-Encoding header field, https://tools.ietf.org/html/rfc7231#section-5.3.4 states: A request without an Accept-Encoding header field implies that the user agent has no preferences regarding content-codings. Although this allows the server to use any con

Re: CoAP support in libcurl for the Internet of Things

2018-04-25 Thread Remy 'Sieben' Leone
Hello, What would be the best approach to offer support for CoAP in the libcurl? - Would you prefer to add support by re-implementing / porting a C library inside libcurl? For instance, most of the CoAP code would be ported from libcoap or another C library directly inside libcurl. It would repre