Skip to content
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

Enforce max message size with mutiple content frames #1566

Merged
merged 1 commit into from
May 16, 2024

Conversation

lukebakken
Copy link
Contributor

Fixes #1356

@lukebakken lukebakken self-assigned this May 14, 2024
@lukebakken lukebakken added this to the 7.0.0 milestone May 14, 2024
@lukebakken lukebakken marked this pull request as ready for review May 15, 2024 15:46
@lukebakken lukebakken force-pushed the rabbitmq-dotnet-client-1356 branch 2 times, most recently from 6505464 to 6f08c29 Compare May 16, 2024 02:37
Fixes #1356

* Fix `TestProperties` test so that expected / actual are correct args.
* Fix passing MaxInboundMessageBodySize via connection config
* Make default RMQ max message size constant Internal
* Ensure that maximum max message size is not overriden
@lukebakken lukebakken force-pushed the rabbitmq-dotnet-client-1356 branch from 6f08c29 to c63959f Compare May 16, 2024 02:39
@lukebakken lukebakken merged commit e52d703 into main May 16, 2024
6 checks passed
@lukebakken lukebakken deleted the rabbitmq-dotnet-client-1356 branch May 16, 2024 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MaxMessageSize actually limits frame size
1 participant