mirror of
https://github.com/searxng/searxng.git
synced 2025-07-31 14:33:50 -04: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>
27 lines
691 B
Plaintext
27 lines
691 B
Plaintext
location ${SEARXNG_URL_PATH} {
|
|
|
|
proxy_pass http://${SEARXNG_INTERNAL_HTTP};
|
|
|
|
proxy_set_header Host \$host;
|
|
proxy_set_header Connection \$http_connection;
|
|
|
|
# see flaskfix.py
|
|
proxy_set_header X-Scheme \$scheme;
|
|
proxy_set_header X-Script-Name ${SEARXNG_URL_PATH};
|
|
|
|
# see limiter.py
|
|
proxy_set_header X-Real-IP \$remote_addr;
|
|
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
|
|
|
|
# proxy_buffering off;
|
|
# proxy_request_buffering off;
|
|
# proxy_buffer_size 8k;
|
|
|
|
}
|
|
|
|
# To serve the static files via the HTTP server
|
|
#
|
|
# location ${SEARXNG_URL_PATH}/static/ {
|
|
# alias ${SEARXNG_STATIC}/;
|
|
# }
|