On 2/18/2015 10:43 PM, Jon wrote:
I have tested this on multiple occasions with the same error but yet
things continue to work. Is this a documented benign error and/or can
I ignore it? Or does it signal something more serious? Am I missing a
setup call?
Also it occurs to me you're
On 2/18/2015 10:43 PM, Jon wrote:
In the following simple code below, I get a CURLE_WRITE_ERROR (23) on
the return of the CURL_EASY_PERFORM function. This looks like a
serious error (error text = failed writing received data to
disk/application) however the data successfully was sent and
Correctly check for memcmp() return value (it returns 0 if the strings match).
This is not really important, since curl is going to use http/1.1 anyway, but
it's still a bug I guess.
Cheers
From 29ad3e7659beb5b85709ac1c3df6a6ac3b11a7b9 Mon Sep 17 00:00:00 2001
From: Alessandro Ghedini
I tested one of our website from my linux-client (curl 7.35.0) for an
directory-traversal issue. I determined, that curl in the version I'm using
it, is not sending the ../../-part of the URL in the GET-Request. I was
confused. I verified, if there are some curl-options to force/allow the
On Thu, 19 Feb 2015, Tom Tom wrote:
A bit weirdly sent email there as it looked like you said this, when in
reality this is what I sent to you privately:
Sure, I can see us adding an option that would prevent curl from doing that
- if you do the work it is even more likelier to happen soon!
Steve, many thanks! Your thinking makes total sense to me after looking at
the code. Socks5/proxy are indeed separate. I just checked our legal
counsel. Unfortunately our policy does not allow me to contribute code into
libcurl. I am sorry about that. It would be great if someone else can help
to
On Mon, 16 Feb 2015, Kamil Dudka wrote:
... even if the last IPv6 connection attempt has failed.
The happy-eyeballs logic is really tricky to follow but I couldn't spot any
problems in your patches and I could run all tests just fine locally with them
applied.
I say go ahead and push,
On Wed, 18 Feb 2015, Jon wrote:
In the following simple code below, I get a CURLE_WRITE_ERROR (23) on the
return of the CURL_EASY_PERFORM function. This looks like a serious error
(error text = failed writing received data to disk/application) however the
data successfully was sent and
On Mon, 12 Jan 2015, Brad King wrote:
I've split the complete patch up into two patches with separate commit
messages.
Thanks a lot for this and sorry for the huge delay. I've now pushed these two
patches.
--
/ daniel.haxx.se
Correctly check for strncmp() return value (it returns 0 if the strings match).
Cheers
From 297c266f33ffb25e017bc005654ab3984da9b3e5 Mon Sep 17 00:00:00 2001
From: Alessandro Ghedini alessan...@ghedini.me
Date: Thu, 19 Feb 2015 19:55:59 +0100
Subject: [PATCH] polarssl: fix ALPN protocol
On Thu, 19 Feb 2015, Alessandro Ghedini wrote:
Correctly check for memcmp() return value (it returns 0 if the strings
match).
Thanks a lot Alessandro, merged and pushed both your fixes now. I prefer
having the code like if(!strncmp(...) instead of comparing == 0 so I edited
them slightly.
Hi friends,
We got this suggested cmake fix and I'll appreciate thumbs up or down for
it...
-- Forwarded message --
Date: Wed, 18 Feb 2015 23:19:25
From: Ben Boeckel notificati...@github.com
You can view, comment on, or merge this pull request online at:
Hello sirs,
So i have one problem, when i follow this example
http://curl.haxx.se/libcurl/c/sendrecv.html
don't return headers of response, how i can return headers ?
cheers
--
I'm not the nicest bloke you've ever met, but I
On Thu, 19 Feb 2015, Cooler_ wrote:
So i have one problem, when i follow this example
http://curl.haxx.se/libcurl/c/sendrecv.html don't return headers of
response, how i can return headers ?
That example make use of curl_easy_send() and curl_easy_recv(). They read and
write raw data from
On 2/19/2015 8:30 PM, Jon wrote:
Thanks Ray for looking into this. I commented out all of the backend
PHP stuff just to see if anything changed but still received the same
error msg. (and things keep on working). I’ll turn on VERBOSE and see
what occurs there.
Note that I’m using build
Hello All,
I've moved inclusion of mprintf.h header into test.h to prevent future
issues with MSVC builds.
Without this header msvc unable to link tests.
This change also will reduce chance of error when adding new tests, which
are using snprintf function.
--
Best Regards,
Sergei Nikulov
The gnutls backend fails to build if HTTP2 support is enabled.
Cheers
From ea414c51a88310e42f48dfc4bfb54c91f992b3af Mon Sep 17 00:00:00 2001
From: Alessandro Ghedini alessan...@ghedini.me
Date: Thu, 19 Feb 2015 16:44:27 +0100
Subject: [PATCH] gtls: fix build with HTTP2
---
lib/vtls/gtls.c | 4
On Thu, 19 Feb 2015, Alessandro Ghedini wrote:
The gnutls backend fails to build if HTTP2 support is enabled.
Thanks a lot, merged and pushed!
--
/ daniel.haxx.se
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Thanks Ray for looking into this. I commented out all of the backend PHP stuff
just to see if anything changed but still received the same error msg. (and
things keep on working). I’ll turn on VERBOSE and see what occurs there.
Note that I’m using build 7.39 via MSVC 11 on Windows 7 x64 as
19 matches
Mail list logo
