mirror of
https://github.com/searxng/searxng.git
synced 2025-08-01 01:22: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>
23 lines
630 B
Text
23 lines
630 B
Text
location ${SEARXNG_URL_PATH} {
|
|
|
|
uwsgi_pass unix://${SEARXNG_UWSGI_SOCKET};
|
|
|
|
include uwsgi_params;
|
|
|
|
uwsgi_param HTTP_HOST \$host;
|
|
uwsgi_param HTTP_CONNECTION \$http_connection;
|
|
|
|
# see flaskfix.py
|
|
uwsgi_param HTTP_X_SCHEME \$scheme;
|
|
uwsgi_param HTTP_X_SCRIPT_NAME ${SEARXNG_URL_PATH};
|
|
|
|
# see limiter.py
|
|
uwsgi_param HTTP_X_REAL_IP \$remote_addr;
|
|
uwsgi_param HTTP_X_FORWARDED_FOR \$proxy_add_x_forwarded_for;
|
|
}
|
|
|
|
# To serve the static files via the HTTP server
|
|
#
|
|
# location ${SEARXNG_URL_PATH}/static/ {
|
|
# alias ${SEARXNG_STATIC}/;
|
|
# }
|