searxng/searx/botdetection/http_sec_fetch.py, branch custom

[mod] drop: from future import annotations

2025-09-03T11:37:36Z

Signed-off-by: Markus Heiser

[mod] limiter: trusted proxies (#4911)

2025-08-09T21:03:30Z

Replaces `x_for` functionality with `trusted_proxies`. This allows defining which IP / ranges to trust extracting the client IP address from X-Forwarded-For and X-Real-IP headers. We don't know if the proxy chain will give us the proper client address (REMOTE_ADDR in the WSGI environment), so we rely on reading the headers of the proxy before SearXNG (if there is one, in that case it must be added to trusted_proxies) hoping it has done the proper checks. In case a proxy in the chain does not check the client address correctly, integrity is compromised and this should be fixed by whoever manages the proxy, not us. Closes: - https://github.com/searxng/searxng/issues/4940 - https://github.com/searxng/searxng/issues/4939 - https://github.com/searxng/searxng/issues/4907 - https://github.com/searxng/searxng/issues/3632 - https://github.com/searxng/searxng/issues/3191 - https://github.com/searxng/searxng/issues/1237 Related: - https://github.com/searxng/searxng-docker/issues/386 - https://github.com/inetol-infrastructure/searxng-container/issues/81

[fix] sec-fetch-* headers cannot be verified for non-secure requests (#4962)

2025-06-30T11:31:45Z

Signed-off-by: Markus Heiser

[fix] sec-fetch-* blocking infinite scroll (#4728)

2025-05-07T08:38:21Z

[fix] references from searx.botdetection.http_sec_fetch (#4723)

2025-05-07T08:25:47Z

fix: check if the browser supports Sec-Fetch headers (#4696)

2025-05-04T08:12:25Z

[mod] botdetection: HTTP Fetch Metadata Request Headers

2025-05-04T00:07:26Z

HTTP Fetch Metadata Request Headers [1][2] are used to detect bot requests. Bots with invalid *Fetch Metadata* will be redirected to the intro (`index`) page. [1] https://www.w3.org/TR/fetch-metadata/ [2] https://developer.mozilla.org/en-US/docs/Glossary/Fetch_metadata_request_header Signed-off-by: Markus Heiser