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
According to the official documentation on version 0.12.3, is states:
Currently, both servers and clients can be configured to set the max message encoding and decoding size. This will ensure that an incoming gRPC message will not exhaust the systems memory. By default, the decoding message limit is 4MB and the encoding limit is usize::MAX.
On the server side, we can configure these limits directly within the service, using max_decoding_message_size and max_encoding_message_size.
However, I don’t see any documented examples of how to configure these limits for the client side, nor can I find any references in the source code.
The text was updated successfully, but these errors were encountered:
According to the official documentation on version
0.12.3
, is states:On the server side, we can configure these limits directly within the service, using
max_decoding_message_size
andmax_encoding_message_size
.However, I don’t see any documented examples of how to configure these limits for the client side, nor can I find any references in the source code.
The text was updated successfully, but these errors were encountered: