You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please see the FAQ in our main README.md before submitting your issue.
Use case(s) - what problem will this feature solve?
This grpc compression document describes compression asymmetry. When attempting to set grpc-encoding in the response metadata, I found the header not getting propagated since it is reserved. This behavior is confirmed here, excerpting:
Server-side, registered compressors will be used automatically to decode request messages and encode the responses. Servers currently always respond using the same compression method specified by the client.
It would be great to have functionality to vary the request vs. response compression for a server.
For more detail, I'm proxying compressed requests (without decompressing/recompressing) to backends that themselves provide asymmetric request-responses.
Proposed Solution
Allow for manual setting of grpc-encoding (and possibly other) headers to allow for explicit control over request/response encoding.
Alternatives Considered
Additional Context
The text was updated successfully, but these errors were encountered:
Please see the FAQ in our main README.md before submitting your issue.
Use case(s) - what problem will this feature solve?
This grpc compression document describes compression asymmetry. When attempting to set
grpc-encoding
in the response metadata, I found the header not getting propagated since it is reserved. This behavior is confirmed here, excerpting:It would be great to have functionality to vary the request vs. response compression for a server.
For more detail, I'm proxying compressed requests (without decompressing/recompressing) to backends that themselves provide asymmetric request-responses.
Proposed Solution
Allow for manual setting of
grpc-encoding
(and possibly other) headers to allow for explicit control over request/response encoding.Alternatives Considered
Additional Context
The text was updated successfully, but these errors were encountered: