[mod] remove option ui.static_use_hash (cache busting) (#5004)

mirror of https://github.com/searxng/searxng.git synced 2026-06-02 16:07:41 +02:00

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 <markus.heiser@darmarit.de>

This commit is contained in:

Markus Heiser

2025-07-11 16:53:36 +02:00

committed by

GitHub

parent 9149175ff2

commit 574b285efa

19 changed files with 62 additions and 104 deletions

									
										utils/templates/etc/searxng/settings.yml
									
		-3
	
												View File
												
				@@ -25,9 +25,6 @@ valkey:

				  # URL to connect valkey database. Is overwritten by ${SEARXNG_VALKEY_URL}.

				  url: valkey://localhost:6379/0

				ui:

				  static_use_hash: true

				# preferences:

				#   lock:

				#     - autocomplete