Join GitHub today
gRPC servers cannot use dynamic HPACK #2405
NGINX Ingress controller version: 0.13.0
I ran a golang gRPC server behind an nginx ingress. Many (but not all) RPCs fail with 502. nginx logs show "upstream sent invalid http2 table index: 64 while reading response header from upstream".
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
(since this is an upstream bug, I'm not including full repro)
Anything else we need to know:
This is a bug in nginx (https://trac.nginx.org/nginx/ticket/1538#ticket), I'm posting a bug here for reference.
That being said, using a grpc-go built from the PR head would solve this issue.
Anyway, this is a bug outside of ingress-nginx. I just wanted to leave a note
There is a workaround that fixes this issues https://trac.nginx.org/nginx/ticket/1397#comment:13
@aledbf I see that the change made it into the 1.15.3 release and I am using 0.19.0, however, I am still getting the following error while trying to use GRPC: