mirror of
https://github.com/searxng/searxng.git
synced 2025-07-12 07:49:22 +02:00
574b285efa
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> |
||
|---|---|---|
| .. | ||
| index.rst | ||
| settings.rst | ||
| settings_brand.rst | ||
| settings_categories_as_tabs.rst | ||
| settings_engines.rst | ||
| settings_general.rst | ||
| settings_outgoing.rst | ||
| settings_plugins.rst | ||
| settings_redis.rst | ||
| settings_search.rst | ||
| settings_server.rst | ||
| settings_ui.rst | ||
| settings_valkey.rst | ||