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.
Support for content-type: application/grpc-web-text
See original GitHub issueSo I was trying to use the in-process proxy to wrap my grpc-server to receive grpc-web requests. I formerly used envoy and it worked with the same client javascript code, however I am running into an issue with the grpc-web-text content-type. Is that content-type actually supported? I saw that there is some string replaced inside the wrapper :
Effectively this converts the context header from application/grpc-web-text to application/grpc-text, which GRPC does not like ( it returns invalid gRPC request content-type ). After replacing that with application/grpc+json, via a wrapper, the grpc handler is successfully continuing, just to later fail with the message: “grpc: received message larger than max (1094795585 vs. 4194304)”
I suspect that grpc-web-text is just not supported at this point and so the necessary steps to transform it aren’t happening thus?
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mier85 This might help: https://github.com/envoyproxy/envoy/blob/10dcbb13d04768cf3e9bbca55ccefc2be0e704ef/source/extensions/filters/http/grpc_web/grpc_web_filter.cc#L78. It’s the source for the C++ proxy that
grpc/grpc-webuses, which supports the base64 text content type.@JBetser, forgive me, but have you tried simply using the binary encoding option? Or using the client in this repo? Both should work with the proxy.