On Wed, 13 Apr 2016, Ameya Vaidya (amevaidy) wrote:
Bumping the thread.
Argh, thanks for that. It had completely slipped through the cracks here. Can
you please submit an issue for this at https://github.com/curl/curl/issues ?
That way it isn't as easily forgotten - even if there's no
Bumping the thread.
> On 11-Mar-2016, at 3:46 am, Daniel Stenberg wrote:
>
>> Any comments on the patch in my previous mail?
>
> I've not had a chance to look at it yet.
---
List admin:
On Thu, 10 Mar 2016, Ameya Vaidya (amevaidy) wrote:
Any comments on the patch in my previous mail?
I've not had a chance to look at it yet.
--
/ daniel.haxx.se
---
List admin: https://cool.haxx.se/list/listinfo/curl-library
Any comments on the patch in my previous mail?
Regards,
- Ameya
> On 07-Mar-2016, at 3:16 pm, Ameya Vaidya (amevaidy)
> wrote:
>
>> To me it sounds like a decent way to fix this problem, so please by all
>> means show us your take!
>
> I take it that pipelining is required to trigger this, isn't it?
That is correct.
>
> To me it sounds like a decent way to fix this problem, so please by all means
> show us your take!
>
--- curl-7.47.1.orig/lib/http.h 2016-02-02 15:02:44.0 -0800
+++ curl-7.47.1/lib/http.h
On Sat, 5 Mar 2016, Ameya Vaidya (amevaidy) wrote:
[Repro Steps]
I take it that pipelining is required to trigger this, isn't it?
Introduce a “DOING” phase for HTTPs. I have prototype code for this fix and
it seems to be working fine for our use-case. I’d like the members’ opinion
on
[Bug Summary]
Making pipelined HTTPs requests to a web server with a custom HTTPs client
built on top of libcurl with openssl for TLS/SSL layer.
Whenever SSL_write() returns SSL_ERROR_WANT_WRITE or SSL_ERROR_WANT_READ, the
connection gets broken and a new connection is established.
[Repro