From cf43d90beb10b249cb052145d75026073e242457 Mon Sep 17 00:00:00 2001 From: jklein Date: Thu, 27 Aug 2026 21:13:08 +0200 Subject: [PATCH] searxng: state the limiter probe measurement instead of hedging it The comment on the probe block said a probe on "/" would "risk" a 429 once the limiter is on. It was measured against a reachable Valkey in k3d and it does not risk it, it collects one: "/" answered 429 while /healthz answered 200. Comment only, no rendered change. --- searxng/values.yaml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/searxng/values.yaml b/searxng/values.yaml index 384399b..6861601 100644 --- a/searxng/values.yaml +++ b/searxng/values.yaml @@ -187,10 +187,13 @@ searxng: # # For it: /healthz is the ONLY path SearXNG's bot detection lets through # unconditionally - searx/limiter.py filter_request() returns early on - # exactly this path before any of its checks run. A probe on "/" would risk - # collecting a 429 the moment settings.limiter is switched on; the pod would - # go NotReady and the symptom would point at the application instead of at - # the bot detection. It also costs nothing: the handler is + # exactly this path before any of its checks run. This is not a theoretical + # margin. Measured in k3d against a reachable Valkey with settings.limiter + # true: "/" answered 429 while /healthz answered 200. A probe on "/" would + # therefore not merely risk a 429, it would collect one the moment the + # limiter is switched on - the pod would go NotReady and the symptom would + # point at the application instead of at the bot detection. It also costs + # nothing: the handler is # `return Response('OK', mimetype='text/plain')`, no engines, no cache, no # network - so liveness carries no external dependency (README, "Values that # must not lie", point 3).