Make content_length_limit configurable #24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently
content_length_limitis hardcoded to 16KB, leading to errors of kindwhen trying to simulate batched intent beauties like https://etherscan.io/tx/0x8d1feb91a6ca9398607b7f02177b61425b1a64d511fcccb9ef7a60becdde0a7b
This PR adds an optional config value that allows to configure this value and allow processing larger request bodies.
Test Plan
Above mentioned transaction simulates successfully when
MAX_REQUEST_SIZE=32