From 0fcdd18136e984171850c01512a35fc7488afe0e Mon Sep 17 00:00:00 2001 From: josh Date: Mon, 14 Sep 2026 21:14:38 -0400 Subject: [PATCH] Fix HTTP 413 (redux): BODY_SIZE_LIMIT="Infinity", not "0" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The adapter treats "0" as "block anything > 0 bytes" rather than "unlimited" — SvelteKit's own error message says: "To disable body size limits, specify Infinity rather than 0." Previous commit set "0", which kept the 413 in place. --- docker-compose.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 9fac8a2..80a365b 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -20,9 +20,12 @@ services: # SvelteKit's Node adapter caps request bodies at 512KB by default, # which rejects real-world plugin .dll uploads with HTTP 413. Same # trust boundary as the CSRF disable (see svelte.config.js) — this is - # LAN-only, so 0 = unlimited is fine. If exposed to the public - # internet, replace with a concrete byte cap instead. - BODY_SIZE_LIMIT: "0" + # LAN-only, so "Infinity" (no cap) is fine. NOTE: "0" does NOT mean + # unlimited in this adapter — it blocks anything > 0 bytes. SvelteKit's + # own error message calls this out: "To disable body size limits, + # specify Infinity rather than 0." If exposed to the public internet, + # replace with a concrete byte cap (e.g. "128M") instead. + BODY_SIZE_LIMIT: "Infinity" SERVERS_ROOT: /root/zombies/t5 REL_DEST: runtime/plutonium/storage/t5/raw/scripts/sp BETA_ARCHIVE_DIR: /root/zombies/beta-archive