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 --- tests/unit/test_webapp.py | 3 --- 1 file changed, 3 deletions(-) (limited to 'tests') diff --git a/tests/unit/test_webapp.py b/tests/unit/test_webapp.py index 35a41302c..91c6309fc 100644 --- a/tests/unit/test_webapp.py +++ b/tests/unit/test_webapp.py @@ -25,9 +25,6 @@ class ViewsTestCase(SearxTestCase): # pylint: disable=too-many-public-methods pass self.setattr4test(searx.search.processors, 'initialize_processor', dummy) - # remove sha for the static file so the tests don't have to care about - # the changing URLs - self.setattr4test(searx.webapp, 'static_files', {}) # set some defaults test_results = [ -- cgit v1.2.3