From f0c3fdfe3a16426fc4bb19e147fca54700359983 Mon Sep 17 00:00:00 2001
From: timedout <git@nexy7574.co.uk>
Date: Fri, 27 Mar 2026 00:54:17 +0000
Subject: [PATCH] fix: Well-known read errors no longer crash resolver flow

Reviewed-By: Jade Ellis <jade@ellis.link>
---
 src/service/resolver/well_known.rs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/service/resolver/well_known.rs b/src/service/resolver/well_known.rs
index c07549ca5..f72e4e8b4 100644
--- a/src/service/resolver/well_known.rs
+++ b/src/service/resolver/well_known.rs
@@ -26,7 +26,10 @@ pub(super) async fn request_well_known(&self, dest: &str) -> Result<Option<Strin
 		return Ok(None);
 	}
 
-	let text = response.limit_read_text(8192).await?;
+	let Ok(text) = response.limit_read_text(8192).await else {
+		debug!("failed to read well-known response (too large or non-text content)");
+		return Ok(None);
+	};
 	trace!("response text: {text:?}");
 
 	let body: serde_json::Value = serde_json::from_str(&text).unwrap_or_default();