-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SendMaxBytes config option #330
Labels
enhancement
New feature or request
Comments
@pkwarren are you still interested in taking this on? Totally fine if not, but I don't want to keep Matt waiting too long. |
I've got most of this wired up - should have an update soon. |
pkwarren
added a commit
that referenced
this issue
Aug 5, 2022
In addition to ReadMaxBytes, add a SendMaxBytes option which will configure the maximum payload sent by clients or handlers. Fixes #330.
pkwarren
added a commit
that referenced
this issue
Aug 5, 2022
In addition to ReadMaxBytes, add a SendMaxBytes option which will configure the maximum payload sent by clients or handlers. Fixes #330.
akshayjshah
pushed a commit
that referenced
this issue
Aug 29, 2022
In addition to ReadMaxBytes, add a SendMaxBytes option which will configure the maximum payload sent by clients or handlers. Fixes #330.
akshayjshah
pushed a commit
that referenced
this issue
Jul 26, 2023
In addition to ReadMaxBytes, add a SendMaxBytes option which will configure the maximum payload sent by clients or handlers. Fixes #330.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In https://github.com/bufbuild/connect-go/pull/311, a ReadMaxBytes option was added, but to go along with that, when you control both the client and server, an equivalent SendMaxBytes (mostly relevant for the client) to pair with ReadMaxBytes would be nice and prevent sending anything over the wire.
In our case, we configure ReadMaxBytes on the server, and would like to pair this also on our client so if a user attempts to send a message that is too large (and would ultimately be rejected by the server anyways), we can bail early on the client before doing any extra work.
This coincides with the gRPC
MaxCallSendMsgSize
option.The text was updated successfully, but these errors were encountered: