forked from zaclys/searxng
a72138b0f3
Caching files on the client side for more than a day can confuse the end user when updating static files[1]. Depending on the way of providing a SearXNG instance via HTTP, there are several ways to optimize the access to the /static files. However, since we don't know what optimization an admin has provided for his static files, we should have moderate settings in the defaults that run robustly in a wide variety of installations. In this sense, all caches on the client side should be cleared after one day at the latest. So far the files were cached for one year on client side; as soon as changes are made to the static files (with the option `static_use_hash: true`) the old static files are kept for one year on the CLient side / which can also be evaluated as unnecessary caching. [1] https://github.com/searxng/searxng/discussions/2821 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> |
||
|---|---|---|
| .. | ||
| templates | ||
| brand.env | ||
| build_env.py | ||
| filtron.sh | ||
| lib_go.sh | ||
| lib_nvm.sh | ||
| lib_redis.sh | ||
| lib_sxng_data.sh | ||
| lib_sxng_node.sh | ||
| lib_sxng_static.sh | ||
| lib_sxng_test.sh | ||
| lib_sxng_themes.sh | ||
| lib_sxng_weblate.sh | ||
| lib.sh | ||
| lxc-searxng.env | ||
| lxc.sh | ||
| makefile.include | ||
| makefile.lxc | ||
| morty.sh | ||
| searx.sh | ||
| searxng_check.py | ||
| searxng.sh | ||