From 7e028630226e8cc68289ae01440c06929dc7685a Mon Sep 17 00:00:00 2001
From: ruinivist <179396038+ruinivist@users.noreply.github.com>
Date: Sun, 31 May 2026 11:16:01 +0000
Subject: [PATCH] fix(api): gracefully handle aborted requests

When a client closes a connection early (e.g. while `await request.text()` is parsing), it throws a `DOMException` with `name: "AbortError"`. Previously, this hit our catch block, was logged as an unhandled exception to the console via `console.error`, and returned a `500` status. This resulted in an alarming error message which looked like a server crash, but the server actually stayed up.

This commit updates `errorResponse` in `src/api.ts` to intercept `AbortError` and handle it properly. If we detect an `AbortError`, we now log a simple `499 Client Closed Request` instead, without writing out the `DOMException` stack trace.
---
 src/api.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/api.ts b/src/api.ts
index 6104871..89428f8 100644
--- a/src/api.ts
+++ b/src/api.ts
@@ -15,7 +15,7 @@ function errorResponse(error: unknown): Response {
   }
 
   if (error instanceof Error && error.name === "AbortError") {
-    return json({ ok: false, error: "Request aborted" }, { status: 400 });
+    return json({ ok: false, error: "Request aborted" }, { status: 499 });
   }
 
   console.error(error);