curl-library
Re: Large POST requests get stuck when sent with HTTP/2 (works with HTTP 1.1)
Date: Fri, 19 Apr 2019 08:37:10 -0700
On Fri, Apr 19, 2019, 8:19 AM Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Thu, 18 Apr 2019, Dmitri Trembovetski via curl-library wrote:
>
> > I've compiled libcurl with HTTP/2 support (openssl, nghttp2) for my
> project.
> > curl 7.56.1 (although I had the same issue with the latest, I backed out
> to
> > that one due to unrelated issue with gzip encoding in the latest)
>
> I would strongly urge you to not spend a lot of time debugging HTTP/2 on
> that
> old release. We've fixed several HTTP/2 issues since then so you risk
> ending
> up chasing things or seeing symptoms that aren't present in the current
> code.
>
> Can you write up a smallish example code that reproduces the problem? If I
> could point such a thing on my own test server I could take a look at it
> from
> my side. HTTP/2 debugging can be a bit complicated.
>
Ok I'll try.
> > With app level logging I can see that CURLOPT_READFUNCTION callback gets
> > invoked up until the point where another GET request happens, and then I
> see
> > no callbacks anymore, and the connection eventually times out or is
> closed
> > by the server.
>
> This symptom matches a previous bug we had (and fixed) in curl's HTTP/2
> code.
>
Ok, I'll retest on the latest release and report back (but I do think I
saw the same issue on the latest).
Also as I mentioned I had an issue with gzip encoding on that release
(goes away if I don't accept gzip encoding). I'll write it up in a separate
email.
Thanks,
Dmitri
> --
>
> / daniel.haxx.se
>
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-04-19