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
grpc-java will check the grpc-accept-encoding header which client send to server and compression is not enabled by default. Compressor will be set with the grpc-accept-encoding message compression method
I believe the discrepancy is due to grpc/grpc-go#2786. Go only recently (grpc/grpc-go#3139) added the client-side setting of grpc-accept-encoding, and the open issue identifies that some more items still remain to be done there.
Since this seems to be more of a gRPC Go question - as far as I can tell, gRPC Java is compliant with the spec and compression is advertised/configured as expected - I'm going to mark this closed here. If there's other Java-specific concerns feel free to comment and I will reopen; otherwise for the Go side of things adding a comment to grpc/grpc-go#2786 is probably the right place.
Client:
grpc-java append
grpc-accept-encoding
header even if compress calloption has not set.grpc-java/core/src/main/java/io/grpc/internal/ClientCallImpl.java
Line 196 in cc2d376
grpc-go append
grpc-accept-encoding
header only if compress calloption has set.https://github.com/grpc/grpc-go/blob/a6ab4473c5a469332c1bdee691293affeaaece25/internal/transport/http2_client.go#L444
Server:
grpc-java will check the
grpc-accept-encoding
header which client send to server and compression is not enabled by default. Compressor will be set with thegrpc-accept-encoding
message compression methodgrpc-java/core/src/main/java/io/grpc/internal/ServerCallImpl.java
Line 114 in cc2d376
grpc-go will not check the
grpc-accept-encoding
header which client send to server and compression is enabled by default. Compressor will be set with thegrpc-encoding
message compression methodhttps://github.com/grpc/grpc-go/blob/a6ab4473c5a469332c1bdee691293affeaaece25/server.go#L1123
Why? Are there any other reasons for the inconsistency?
The text was updated successfully, but these errors were encountered: