Remove payload length cap from Event Stream messages #3371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In initial implementations of Event Streams, there was a 16MB payload limit for Event Stream payloads. Anything exceeding that was considered malformed. In more modern implementations, that limit has been raised with some services using 24MB. We'll be removing this client-side check going forward as it doesn't serve a practical purpose. The checksum will be used to validate the payload and size limitations will be left to the service to determine going forward.