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.

Use lower case header keys in in-body trailers as mandated by gRPC-Web spec.

See original GitHub issue

I found some concerns when I have tested a gRPC Web server related to trailers.

here are the response trailers.

Content-Type: application/grpc+proto
Grpc-Status: 0

Why aren’t trailer names using lower-case? The gRPC Web spec says, “use lower-case header/trailer names”.
Why is Grpc-Status at the end? In order to the ABNF of gRPC response, Status must be next to Length-Prefixed-Message.

ref. https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-WEB.md https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md

Issue Analytics

State:
Created 5 years ago
Comments:13 (3 by maintainers)

Top GitHub Comments

1reaction

johanbrandhorstcommented, Nov 3, 2018

I’m my testing of 0.6.4 in https://github.com/johanbrandhorst/grpc-web-compatibility-test this is now working as expected 🎉. Huge thanks to @ktr0731 for getting the ball rolling on this!

1reaction

johanbrandhorstcommented, Oct 25, 2018

@ktr0731 I’ve created a repo that should help test this behaviour: https://github.com/johanbrandhorst/grpc-web-compatibility-test. If you’re interested in testing this more, maybe you could contribute to the repo?