Introduce a configurable limit to HTTP API request body size

[michaelklishin]

The default is 10 MiB, enough to import a definition file with 100K queues over the HTTP API, or publish a message over the HTTP API (something that is highly discouraged) close to 10 MiB in size.

Note that rabbitmqctl import_definitions and boot time node-local definition import are not affected, only the HTTP API is.

To override the limit (if you are really sure you need to do this):

# In rabbitmq.conf, this bumps the limit to 20 MiB
management.http.max_body_size = 20000000

[qlong1505]

Hi @michaelklishin
At file deps/rabbitmq_management/src/rabbit_mgmt_util.erl, line 693

case bit_size(Acc) > BodySizeLimit of

If I set in rabbitmq.conf file as management.http.max_body_size = 20000000, does it means that the maximum body size is only set at about 20Mbit base on the logic above? From the beginning I assume it is MiB but I always received

{
    "error": "bad_request",
    "reason": "Exceeded HTTP request body size limit"
}

when trying to push a msg size 15MB via http API. If I change the ``management.http.max_body_size = 160000000` then I receive

{"routed":true}

[michaelklishin]

@qlong1505 the value is in bytes, as the name suggests. The computed body size is also in bytes.

The limit is meant to help you establish a guard rail, not allow for super fine grained control down to the byte.

Please use GitHub Discussions for questions. And consumer publishing using a regular messaging client and not the HTTP API, in particular for large messages.