Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Healthchecks for destinations running on HTTP1.1 and HTTP/2

See original GitHub issue

I use the YARP as gRPC balancer based on of course on HTTP/2. My destinations gRPC server are not using TLS as all of them is internal. So that’s why I have the following settings in YARP config

"HttpRequest": {
       "Version": "2",
       "VersionPolicy": "RequestVersionExact"
      },

But an endpoints for healthchecks are done as REST API with HTTP1.1 (on dotnet 5.0). So that’s why I’m getting the The HTTP/2 server sent invalid data on the connection. HTTP/2 error code ‘PROTOCOL_ERROR’ (0x1)

Can I somehow workaround it on the YARP side? Thanks

Issue Analytics

State:
Created 2 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

Tratchercommented, Aug 23, 2021

Is there something else that should be done here or can we close this as answered?

There’s a doc update proposed here: https://github.com/microsoft/reverse-proxy/issues/1153#issuecomment-880137670

1reaction

Tratchercommented, Jul 15, 2021

That’s considered unhealthy by both active and passive checks. If a passive check were the first to notice then the first few responses would still get 503s before it was pulled out of rotation. If you don’t have any healthy destinations left then subsequent requests will also get 503s.