tune self-hosted discovery cap

sallyom · sallyom · commit d84f514a1f17 · 2026-06-24T13:58:58.000-04:00
Signed-off-by: sallyom &lt;somalley@redhat.com&gt;
diff --git a/src/plugins/provider-self-hosted-setup.test.ts b/src/plugins/provider-self-hosted-setup.test.ts
@@ -25,7 +25,7 @@ beforeEach(() => {
 
 // Mirrors SELF_HOSTED_DISCOVERY_JSON_MAX_BYTES in the source under test. Kept in
 // sync deliberately so the regression asserts the body is capped, not drained.
-const SELF_HOSTED_DISCOVERY_JSON_MAX_BYTES = 4 * 1024 * 1024;
+const SELF_HOSTED_DISCOVERY_JSON_MAX_BYTES = 16 * 1024 * 1024;
 const CHUNK_BYTES = 1024 * 1024;
 
 /**
diff --git a/src/plugins/provider-self-hosted-setup.ts b/src/plugins/provider-self-hosted-setup.ts
@@ -44,7 +44,7 @@ const log = createSubsystemLogger("plugins/self-hosted-provider-setup");
 // who can influence the configured endpoint, e.g. via SSRF, could serve an
 // unbounded JSON stream). Cap discovery response bodies before parsing so a
 // hostile or buggy endpoint cannot drive the setup wizard into OOM.
-const SELF_HOSTED_DISCOVERY_JSON_MAX_BYTES = 4 * 1024 * 1024;
+const SELF_HOSTED_DISCOVERY_JSON_MAX_BYTES = 16 * 1024 * 1024;
 
 type OpenAICompatModelsResponse = {
   data?: Array<{
