From b8078874a7ebb88c3954f774c9b27ffd6c7ec322 Mon Sep 17 00:00:00 2001
From: Michael Klishin <michaelklishin@icloud.com>
Date: Sat, 15 Mar 2025 18:22:55 -0400
Subject: [PATCH] Increase initial AMQP 0-9-1 connection frame size limit

Before the client authenticates, the standard
frame_max is not used. Instead, the limit is
a special constant.

This is fine for password or x.509 certificate-based
authentication but not for some JWT tokens,
which can vary in size, and take multiple
kilobytes.

8 kB specifically is the default HTTP header
length limit used by Nginx.
Sounds like this value was good enough
for a lot of Bearer headers with JWT tokens.

Closes #13541.
---
 deps/rabbit_common/include/rabbit_framing.hrl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deps/rabbit_common/include/rabbit_framing.hrl b/deps/rabbit_common/include/rabbit_framing.hrl
index fa189d394b25..14a641775228 100644
--- a/deps/rabbit_common/include/rabbit_framing.hrl
+++ b/deps/rabbit_common/include/rabbit_framing.hrl
@@ -11,7 +11,7 @@
 -define(FRAME_HEADER, 2).
 -define(FRAME_BODY, 3).
 -define(FRAME_HEARTBEAT, 8).
--define(FRAME_MIN_SIZE, 4096).
+-define(FRAME_MIN_SIZE, 8192).
 -define(FRAME_END, 206).
 -define(REPLY_SUCCESS, 200).
 -define(CONTENT_TOO_LARGE, 311).