Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Libcurl reports 'Error in the HTTP2 framing layer' (16) for outgoing request.
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 27 May 2021 13:36:52 +0200 (CEST)
On Thu, 27 May 2021, Shikha Sharma via curl-library wrote:
> I am facing an issue where curls responds with error "'Error in the HTTP2
> framing layer' (16)" to the application.
>
> Curl version: libcurl-7.74.0
>
> Scenario: Sending multiple outgoing HTTP2 requests to an external HTTP
> server.
I'm afraid this descripion lacks details to allow us to draw many conclusions.
You also didn't mention if you use h2 over TLS or not and you didn't state
which nghttp2 version you're using.
> So it looks as if its a race condition where the client starts processing
> the new request and creates a stream on the existing connection before the
> goaway frame from the previous connection is processed. The request is
> ultimately dropped and application using libcurl receives the framing error.
If that's true then it sounds like a bug to me. We've fixed several h2 related
bugs since 7.74.0 so I'd recommand you start out by trying the latest curl
version and see if anything gets better.
Date: Thu, 27 May 2021 13:36:52 +0200 (CEST)
On Thu, 27 May 2021, Shikha Sharma via curl-library wrote:
> I am facing an issue where curls responds with error "'Error in the HTTP2
> framing layer' (16)" to the application.
>
> Curl version: libcurl-7.74.0
>
> Scenario: Sending multiple outgoing HTTP2 requests to an external HTTP
> server.
I'm afraid this descripion lacks details to allow us to draw many conclusions.
You also didn't mention if you use h2 over TLS or not and you didn't state
which nghttp2 version you're using.
> So it looks as if its a race condition where the client starts processing
> the new request and creates a stream on the existing connection before the
> goaway frame from the previous connection is processed. The request is
> ultimately dropped and application using libcurl receives the framing error.
If that's true then it sounds like a bug to me. We've fixed several h2 related
bugs since 7.74.0 so I'd recommand you start out by trying the latest curl
version and see if anything gets better.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-05-27