From 32e8c2cf098ae59baae5672e70436e47299bec82 Mon Sep 17 00:00:00 2001 From: Alexandre Flament Date: Tue, 19 Jul 2022 23:40:11 +0200 Subject: searx.network: add "verify" option to the networks Each network can define a verify option: * false to disable certificate verification * a path to existing certificate. SearXNG uses SSL_CERT_FILE and SSL_CERT_DIR when they are defined see https://www.python-httpx.org/environment_variables/#ssl_cert_file --- searx/settings.yml | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'searx/settings.yml') diff --git a/searx/settings.yml b/searx/settings.yml index f21d7f05a..2304c6fe7 100644 --- a/searx/settings.yml +++ b/searx/settings.yml @@ -145,6 +145,11 @@ outgoing: pool_maxsize: 20 # See https://www.python-httpx.org/http2/ enable_http2: true + # uncomment below section if you want to use a custom server certificate + # see https://www.python-httpx.org/advanced/#changing-the-verification-defaults + # and https://www.python-httpx.org/compatibility/#ssl-configuration + # verify: ~/.mitmproxy/mitmproxy-ca-cert.cer + # # uncomment below section if you want to use a proxyq see: SOCKS proxies # https://2.python-requests.org/en/latest/user/advanced/#proxies # are also supported: see -- cgit v1.2.3