From 574b285efa1658fd6d82d673e2063be659d5f624 Mon Sep 17 00:00:00 2001 From: Markus Heiser Date: Fri, 11 Jul 2025 16:53:36 +0200 Subject: [mod] remove option ui.static_use_hash (cache busting) (#5004) Cache busting has caused serious problems for users in the past, here are two examples: - https://github.com/searxng/searxng/issues/4419 - https://github.com/searxng/searxng/issues/4481 And it makes development and deployment significantly more complex because it binds the client side to the server side: - https://github.com/searxng/searxng/pull/4466 In the light of a decoupled development of the WEB clients from the server side: - https://github.com/searxng/searxng/pull/4988 is it appropriate to abandon this feature. In fact, it has been ineffective since #4436 anyway. However, the benefit has always been questionable, since at best only a few kB of data are saved (at least in the context of an image_proxy, the effect is below the detection limit). Ultimately, the client is responsible for caching. Related: https://github.com/searxng/searxng/issues?q=label%3A%22clear%20browser%20cache%22 Closes: https://github.com/searxng/searxng/pull/4466 Closes: https://github.com/searxng/searxng/issues/1326 Closes: https://github.com/searxng/searxng/issues/964 Signed-off-by: Markus Heiser --- searx/settings.yml | 2 -- 1 file changed, 2 deletions(-) (limited to 'searx/settings.yml') diff --git a/searx/settings.yml b/searx/settings.yml index fb85f0ff4..1b6739927 100644 --- a/searx/settings.yml +++ b/searx/settings.yml @@ -119,8 +119,6 @@ valkey: ui: # Custom static path - leave it blank if you didn't change static_path: "" - # Is overwritten by ${SEARXNG_STATIC_USE_HASH}. - static_use_hash: false # Custom templates path - leave it blank if you didn't change templates_path: "" # query_in_title: When true, the result page's titles contains the query -- cgit v1.2.3