As the title states, the web app is failing to make http2 calls to our service, where as the desktop app works flawlessly. Our load balancer is set to accept http2/gRPC, and when making a call from the web app I am getting code 464 in return. I assume this has to do with the web proxy routing my requests.
Thanks for your feedback.
I guess you’re using the web app with the Browser Extensions Agent. Due to browser limitations, Apidog cannot create new HTTP/2 connections, but it can reuse existing connections.
There is a magical solution: open a new tab in Chrome, enter the URL of the HTTP/2 API you want to request in the address bar, and access it.
Then, go back to Apidog, send the request again, and it should work fine.