On 5/8/2014 3:21 AM, Dionysios Kalofonos wrote:
On 5/7/14, 10:14 PM, Ray Satiro wrote:
I'll probably keep issuing custom commands because of my requirements.
With a regular SEARCH I can't get exactly what I want but that's my
problem. If you're going to make changes to FETCH may I suggest
On 5/7/2014 2:19 AM, Satz Klauer wrote:
But I could provide the related root-certificate during the request.
So: how can this be done using libcurl? How should code for a
HTTPS-POST-request look like when a custom root-certificate is used?
Did you try CURLOPT_CAINFO?
curl_easy_setopt( hnd,
On 5/6/2014 6:53 PM, Steve Holme wrote:
On Tue, 06 May 2014, Ray Satiro wrote:
I think the areas we need to look at are as follows:
* Fixed libcurl FETCH API (as you suggested in Option A)
* Change the LIST command be driven off CURLOPT_DIRLISTONLY
* Change current custom commands
On 5/5/2014 2:06 PM, Steve Holme wrote:
I think the areas we need to look at are as follows:
* Fixed libcurl FETCH API (as you suggested in Option A)
* Change the LIST command be driven off CURLOPT_DIRLISTONLY
* Change current custom commands to be an override of LIST
* Implement custom
On 3/28/2014 2:07 PM, Steve Holme wrote:
Am I right in thinking that we currently support building MSVC from
makefiles via:
* makefile.dist - as per testcurl.pl
* makefile.vc6
* winbuild\makefilw.vc
What about cmake, is that method still supported for MSVC? Several
months ago Daniel said it
On 2/20/2014 12:11 PM, Daniel Stenberg wrote:
So here's my latest version of the patch set for CURLOPT_PROXYHEADER.
Now at 7 patches, including 5 new test cases and updated documentation.
I'm curious why not use branches on github for things like this?
On 2/20/2014 5:38 PM, Daniel Stenberg wrote:
On Thu, 20 Feb 2014, Ray Satiro wrote:
I'm curious why not use branches on github for things like this?
Would that really make code reviewing or commenting of my patches easier?
I always have like 30 local branches with development and bug-fixing
How can I get SSL server certificate info from libcurl when a handshake fails?
For the server, using a cert that will fail verification for example:
socat openssl-listen:4433,reuseaddr,cert=fail.pem,verify=0,fork -
For the client, using libcurl 7.33.0:
curl_easy_setopt(curl,
601 - 608 of 608 matches
Mail list logo
