ERR_HTTP2_INVALID_CONNECTION_HEADERS

[dhalbrook]

Is anyone running into occasional issues with HTTP 2 connections receiving HTTP 1 headers?

It's sporadic, but it causes an uncaught exception, but i'm not even sure where'd i'd handle it:

{err":{"type":"TypeError","message":"HTTP/1 Connection specific headers are forbidden: \"http2-settings\"","stack":"TypeError: HTTP/1 Connection specific headers are forbidden: \"http2-settings\"\n    
at mapToHeaders (node:internal/http2/util:651:13)\n    
at ClientHttp2Session.request (node:internal/http2/core:1813:25)\n    
at writeH2 (/.../node_modules/undici/lib/dispatcher/client-h2.js:469:22)\n    
at Object.write (/.../node_modules/undici/lib/dispatcher/client-h2.js:119:14)\n    
at _resume (/.../node_modules/undici/lib/dispatcher/client.js:601:50)\n    
at resume (/.../node_modules/undici/lib/dispatcher/client.js:303:28\n    
at node:internal/process/task_queues:140:7\n    
at AsyncResource.runInAsyncScope (node:async_hooks:206:9)\n    
at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)","code":"ERR_HTTP2_INVALID_CONNECTION_HEADERS"},"msg":"Uncaught exception in NodeJS"}

[metcoder95]

This is Server problem (as the formulated response) not aligning with spec.

[dhalbrook]

Is there a way in Undici to handle this as a runtime error and retry the operation?

[metcoder95]

As is thrown as uncaught exception and given the H2 implementation, this must be a bug as a wrapper around it should be added so you can use an interceptor (e.g. retry) to identify this error and retry the operation.

[dhalbrook]

@metcoder95 Shall I file a bug against this then?

[metcoder95]

Yes please, and a contribution is always welcomed 👍

[dhalbrook]

OK, here's the issue: #4356

I'm on vacation for the next two weeks but after that I'll see if I can come up with a fix.