From 56d51bcf82c5b934aa214f4fc4bae8b3df8a5b2b Mon Sep 17 00:00:00 2001 From: mkdev11 Date: Tue, 6 Jan 2026 06:13:00 +0200 Subject: [PATCH] docs: add comment clarifying translatability of TLS error messages Error messages could be translated, but TLS alert names (e.g., certificate_required) are from RFC 8446 spec and should remain in English for consistency. --- server/monitor-types/tcp.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/server/monitor-types/tcp.js b/server/monitor-types/tcp.js index ca124b400..06a2011f9 100644 --- a/server/monitor-types/tcp.js +++ b/server/monitor-types/tcp.js @@ -314,6 +314,8 @@ class TCPMonitorType extends MonitorType { } // Check if we got the expected alert + // Note: Error messages below could be translated, but alert names (e.g., certificate_required) + // are from RFC 8446 spec and should remain in English for consistency with the spec. if (result.alertName === expectedTlsAlert) { heartbeat.status = UP; heartbeat.msg = `TLS alert received as expected: ${result.alertName} (${result.alertNumber})`;