After upgrading a test cluster from 7.71.1 to 7.72.0, we're now seeing
around 0.1% of POSTs from one (and only one) of our applications fail with
"Failed sending data to the peer" (CURLE_SEND_ERROR) and no other error.
Based on logs, the request actually succeeds, but libcurl is returning this
erro
nnections, and all of this is regular
GETs and POSTs)...
On Fri, Sep 11, 2020 at 10:34 PM Ray Satiro via curl-library <
curl-library@cool.haxx.se> wrote:
> On 9/11/2020 2:03 PM, James Brown via curl-library wrote:
>
> After upgrading a test cluster from 7.71.1 to 7.72.0, we're n
599>
> which
> claims to only affect CONNECT-only connections, and all of this is regular
> GETs and POSTs)...
>
> On Fri, Sep 11, 2020 at 10:34 PM Ray Satiro via curl-library <
> curl-library@cool.haxx.se> wrote:
>
>> On 9/11/2020 2:03 PM, James Brown via curl-libra
I've been running 7.72.0 with that patch cherry-picked for over a day and
the issue has not recurred. There's definitely something spooky going on.
Does extract_if_dead have any other side effects?
On Wed, Sep 16, 2020 at 1:22 AM Daniel Stenberg wrote:
> On Mon, 14 Sep 2020, Ja
This is kind of a longshot, but I've been building curl 7.74 and I notice
that test 3001 keeps flaking on me. It always passes in isolation, but
fails about half the time when running the whole suite. No test other than
3001 has failed for me.
Has anyone else noticed it being flaky?
I attached th
FWIW this fails in the same way with the latest stunnel (5.57) and the
latest ABI-compatible openssl (1.0.2u).
On Thu, Dec 10, 2020 at 3:20 PM Daniel Stenberg wrote:
> On Thu, 10 Dec 2020, James Brown via curl-library wrote:
>
> > This is kind of a longshot, but I've been build
