On Tue, 26 Mar 2013, Steven Gu wrote:
I debug the codes of curl-7.29.0, there is a multi handle is initialized in
the function curl_easy_perform, the maxconnects is not set to the multi
handle. The value of maxconnects of the internal multi handle is always 0.
Now stored as bug #1212:
Hello list,
mk-ca-bundle currently wraps PEM certs at 76 chars. I suspect 64
chars would be more helpful, as it's consistent OpenSSL's (correct)
PEM output. It's a fairly trivial issue, but it may have consequences
of which I'm not aware. Any thoughts?
If ok, below is a patch with comments in
Hi Richard,
On 03.04.2013 19:13, Richard Michael wrote:
mk-ca-bundle currently wraps PEM certs at 76 chars. I suspect 64
chars would be more helpful, as it's consistent OpenSSL's (correct)
PEM output. It's a fairly trivial issue, but it may have consequences
of which I'm not aware. Any
Hello I am developing an application over HTTPS.
My first handshakes related to SSL/TLS takes successfully.
But the problem is in the response, which i store using function as
*curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, WriteMemoryCallback);*
* curl_easy_setopt(curl, CURLOPT_WRITEDATA,
Hello Günter,
A few comments, inlined for readability,
On Wed, Apr 3, 2013 at 10:07 PM, Guenter li...@gknw.net wrote:
Hi Richard,
On 03.04.2013 19:13, Richard Michael wrote:
mk-ca-bundle currently wraps PEM certs at 76 chars. I suspect 64
chars would be more helpful, as it's consistent
Hi Richard,
On 03.04.2013 23:51, Richard Michael wrote:
0/ I am primarily concerned with the format of the CA bundle file, not
with the possibility of parsing the file with an encoder/decoder. I
have not investigated coders other than OpenSSL, but I believe you
[that they will handle 76
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.04.2013 18:20, Dan Fandrich wrote:
On Tue, Apr 02, 2013 at 05:29:10PM +0400, LRN wrote:
24 285 543 571 1309 fail due to \r\n vs \n difference (my guess
is that data is sent over the network with correct EOLS, but curl
client prints it in
On Tue, Mar 26, 2013, Arunav Sanyal arunav.sanya...@gmail.com wrote:
Ok line number 308 is the malloc call which occurs immediately after
the free statement that i talked about. This malloc is never reached,
since the free itself causes a breakpoint after which I cannot step
forward
Daily
Hi everyone on this list
I noticed a problem with curl. When a file is already downloaded completely and
curl is executed again using -C - then curl says curl: (33) HTTP server doesn't
seem to support byte ranges. Cannot resume.
$ curl -C - http://www.heise.de -o heise.de
% Total%
On 04/04/2013 12:19 AM, Ajay Tanpure wrote:
Hello I am developing an application over HTTPS.
My first handshakes related to SSL/TLS takes successfully.
But the problem is in the response, which i store using function as
*curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, WriteMemoryCallback);*
*
10 matches
Mail list logo
