From 65be5615ad6a782a267a41a70059b82e2d1a0b0a Mon Sep 17 00:00:00 2001
From: Jaime Idolpx <jaime@idolpx.com>
Date: Sun, 14 Jun 2026 04:55:28 -0400
Subject: [PATCH] fix(SearchAssembly64): update client-id header to match
 server requirements

---
 src/app/components/SearchAssembly64.tsx | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/app/components/SearchAssembly64.tsx b/src/app/components/SearchAssembly64.tsx
index 104cb49..daa7140 100644
--- a/src/app/components/SearchAssembly64.tsx
+++ b/src/app/components/SearchAssembly64.tsx
@@ -14,7 +14,11 @@ const DOWNLOAD_DIR = '/sd/downloads';
 function leetFetch(path: string, query?: Record<string, string>) {
   const url = new URL(LEET_BASE + path);
   if (query) Object.entries(query).forEach(([k, v]) => url.searchParams.set(k, v));
-  return fetch(url.toString(), { headers: { 'client-id': 'swagger' } });
+  // The server whitelists "Client-Id: Ultimate" (the 1541 Ultimate
+  // cartridge) and rejects unknown client ids with HTTP 464. The server
+  // also advertises "client-id" in Access-Control-Allow-Headers, so the
+  // preflight that this custom header triggers is allowed.
+  return fetch(url.toString(), { headers: { 'Client-Id': 'Ultimate' } });
 }
 
 async function leetJson<T>(path: string, query?: Record<string, string>): Promise<T> {