HTTP API: reduce body size limit for the endpoint used to bind queues/streams/exchanges #12696
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
It does not need to use the "worst case scenario" default HTTP request body size limit that is primarily necessary because definition imports can be large (MiBs in size, for example). Since exchange, queue names and routing key have limits of 255 bytes and optional arguments can practically be expected to be short, we can lower the limit to < 10 KiB.
michaelklishin
changed the title
michaelklishin
changed the title
michaelklishin
changed the title
michaelklishin
deleted the
mk-http-api-lower-body-length-limit-for-binding-creation
branch
michaelklishin
added a commit
that referenced
this pull request
Nov 9, 2024
michaelklishin
added a commit
that referenced
this pull request
Nov 9, 2024
(cherry picked from commit a66c926)
michaelklishin
added a commit
that referenced
this pull request
Nov 9, 2024
HTTP API: reduce body size limit for the endpoint used to bind queues/streams/exchanges (backport #12696)
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.
It does not need to use the "worst case scenario"
default HTTP request body size limit that
is primarily necessary because definition imports
can be large (MiBs in size, for example).
Since exchange, queue names and routing key
have limits of 255 bytes and optional arguments
can practically be expected to be short, we
can lower the limit to < 10 KiB.