Closed eottabom closed 2 months ago
I don't believe Envoy supports grpc compression/decompression at the moment. For non-transcoding cases it shouldn't matter as the payload is passed through. For transcoding, only uncompressed payloads are supported. I agree that a custom http filter should be able to handle compressed payloads, WASM or otherwise.
Is grpc compression/uncompression not allowed in the Envoy document?
If not, I would like to add it.
It would be nice if it stated that it should be treated with the same filter as WASM. I hope that an example will be added as well.
I recommend a short document describing your plan. I think it's probably the case that this would be another http filter.
@zuercher Is this what you want?
I think the gRPC compression on the right can be compressed and sent by the gRPC server.
I think it will be a different http filter as you say.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Title: I need a guide for gRPC compression/decompression.
Description: The filter for compression/decompression works only for http1.1. I would like to know about the guide or method for gRPC compression/uncompression.
If envoy knows proto, it seems that compression and decompression are possible.
I think it will be possible with WASM filter another way.