This message was deleted.

It looks like your client is negotiating an HTTP/2 upgrade but something’s not working about it. You could try disabling HTTP/2 in WireMock so that it won’t attempt protocol changes like this.

How do I do that?

Apologies, I’d (mis)remembered adding a config flag for the HTTP/2 connector, but it seems I didn’t. If you’re starting WireMock from Java you could copy/paste the Jetty HTTP server impl and remove the HTTP/2 connector lines. Another (probably simpler) thing to try is to see if there’s a config option in the Camel client that does one of a) fixing the protocol at HTTP/1.1 or b) disables ALPN.

Ok, thanks for your response.