Re: MBEDTLS d5800b7761ad9705d2ebca86d7af0c8ee24e427a creates regression wher compiling libcurl error: unknown type name 'mbedtls_time_t'

2016-07-02 Thread Dan Fandrich
On Sat, Jul 02, 2016 at 08:32:53PM +0200, Thomas Glanzmann wrote: > Hello, > when I compile libcurl with mbedtls-2.3.0 I hit the following libcurl > compile regression: > > In file included from ../lib/urldata.h:98:0, > from vtls/darwinssl.c:31: >

MBEDTLS d5800b7761ad9705d2ebca86d7af0c8ee24e427a creates regression wher compiling libcurl error: unknown type name 'mbedtls_time_t'

2016-07-02 Thread Thomas Glanzmann
Hello, when I compile libcurl with mbedtls-2.3.0 I hit the following libcurl compile regression: In file included from ../lib/urldata.h:98:0, from vtls/darwinssl.c:31: /home/sithglan/work/vlconnect/curl/../local/win32/include/mbedtls/ssl.h:545:5: error: unknown type name

Re: cacert.pem updates in real time

2016-07-02 Thread Dan Fandrich
On Sat, Jul 02, 2016 at 01:33:23PM +0200, Tim Rühsen wrote: > (Bash me for suggesting to use wget ;-)) > > $ wget -N http-url > > only downloads the file if the timestamp changed. > So there is not much data traffic in the case when the server hasn't a new > one. > > I would run this every X

Re: cacert.pem updates in real time

2016-07-02 Thread Vinayak Tanksale
Our client's customers ran into errors as the web service that we use started complaining of certificate error. So we decided to do daily updates to cacert.pem. However, the client doesn't want to wait up to possibly 24 hours. Thanks. Sent from my iPhone > On Jul 2, 2016, at 5:03 PM, Tim

Re: HTTP2 by default ?

2016-07-02 Thread Daniel Stenberg
On Sat, 2 Jul 2016, Daniel Stenberg wrote: ... but the internal default is HTTP/2 for HTTPS, and HTTP/1.1 for HTTP so this phrasing isn't strictly correct either! Oh, and the defaults were changed to this in the 7.47.0 release when we introduced the CURL_HTTP_VERSION_2TLS option to libcurl

Re: cacert.pem updates in real time

2016-07-02 Thread Tim Rühsen
On Saturday 02 July 2016 08:37:18 Vinayak Tanksale wrote: > How do we know that we need to download a new one? We have an app that uses > cacert.pem and if a new one is issued then the app stops functioning. We > would ideally want as much less downtime as possible. We are downloading > the file

Re: HTTP2 by default ?

2016-07-02 Thread Daniel Stenberg
On Sat, 2 Jul 2016, Tim Rühsen wrote: .IP "--http2" (HTTP) Tells curl to issue its requests using HTTP 2. This requires that the -underlying libcurl was built to support it. (Added in 7.33.0) +underlying libcurl was built to support it - in this case this is the internal +default version.

Re: HTTP2 by default ?

2016-07-02 Thread Tim Rühsen
On Friday 01 July 2016 20:39:36 Daniel Stenberg wrote: > On Fri, 1 Jul 2016, Tim Ruehsen wrote: > > Currently, curl uses HTTP2 by default. > > Yes, the command line tool does that for HTTPS URLs. > > > But the man pages says: use --http2 to switch it on. > > Well, not exactly, but I agree that

Re: cacert.pem updates in real time

2016-07-02 Thread Daniel Stenberg
On Sat, 2 Jul 2016, Vinayak Tanksale wrote: How do we know that we need to download a new one? There's no good answer to that. The cacert file is a list of signatures of the CAs you and your app trust. How often does that change? The file you decide to depend on is updated by mozilla (and