Closed
Description
After #9043, the grpc client can set MaxCallRecvMsgSize when creating a request.
But when the client accesses etcd via http (through the proxy of grpc-gateway), it seems there is not a way to configure grpc.MaxCallRecvMsgSize
?
Metadata
Metadata
Assignees
Labels
No labels
Activity
agargi commentedon Dec 28, 2020
@spacewander Should this not be a gRPC Gateway question? I believe gRPC Gateway may be providing this kind of capability through metadata sent as part of request header.
spacewander commentedon Dec 29, 2020
@agargi
MaxCallRecvMsgSize is a client option, not a metadata name. AFAIK, gRPC Gateway doesn't provide a feature to set it via HTTP request.
stale commentedon Mar 29, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.
spacewander commentedon Mar 29, 2021
Does the problem still exist?
simonhou commentedon May 14, 2021
@spacewander Our apisix use etcd v3.4, still exist.
server: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway
spacewander commentedon Jun 3, 2021
@simonhou
I have just submitted a PR to solve the issue
embed: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway
embed: unlimit the recv msg size of grpc-gateway