HTTP2 error using gun

[Fl4m3Ph03n1x]

@peerreynders

Here I’m just as a clueless as the proverbial rubber duck.

Your help is always welcome, no matter what animal format it may come in

@peerreynders

Found a critical (possibly misinformed) opinion about the practice of HTTP/2 ping frames.

I read the whole thing and I must say that, at least to me, I found some of his arguments convincing. However I am not as well versed in HTTP2 as others are so I am not convinced that 3 negative points about a whole protocol make it utter garbage.

All I can say is I see where he comes from and I thank you for liking me to it.

@peerreynders

The gun documentation suggests that the default HTTP/2 ping timeout is 5000ms.

Indeed ! I am using the default timeout

@peerreynders

Do the errors change when you extend your configured timeout for gun ? (Not expecting it to but it’s good to rule things out).

I have not tried this, but having in mind we have an automatic scaled cluster behind said load balancer, this shouldn’t even be a problem to begin with, right?

@axelson

What cloud balancer is the service using? Perhaps the cloud balancer is doing some rate limiting?

We are using Google Cloud Platform.
It is not unusual for us to get 502 errors from the load balancer (an issue impossible to solve with google) so it can very well be that Google’s services aren’t as resilient as we need.