searxng/.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2021-05-24	[coding-style] searx/network/client.py - normalized indentations	Markus Heiser
	No functional change! Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-05-24	[pylint] searx/network/client.py & add global (TRANSPORT_KWARGS)	Markus Heiser
	No functional change! - fix messages from pylint - add ``global TRANSPORT_KWARGS`` - normalized python_socks imports Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-05-05	[mod] searx.network.client: the same configuration reuses the same ↵	Alexandre Flament
	ssl.SSLContext before there was one ssl.SSLContext per client. see https://github.com/encode/httpx/issues/978
2021-04-27	[fix] searx.network: fix rare cases where LOOP is None	Alexandre Flament
	* searx.network.client.LOOP is initialized in a thread * searx.network.__init__ imports LOOP which may happen before the thread has initialized LOOP This commit adds a new function "searx.network.client.get_loop()" to fix this issue
2021-04-12	[httpx] replace searx.poolrequests by searx.network	Alexandre Flament
	settings.yml: * outgoing.networks: * can contains network definition * propertiers: enable_http, verify, http2, max_connections, max_keepalive_connections, keepalive_expiry, local_addresses, support_ipv4, support_ipv6, proxies, max_redirects, retries * retries: 0 by default, number of times searx retries to send the HTTP request (using different IP & proxy each time) * local_addresses can be "192.168.0.1/24" (it supports IPv6) * support_ipv4 & support_ipv6: both True by default see https://github.com/searx/searx/pull/1034 * each engine can define a "network" section: * either a full network description * either reference an existing network * all HTTP requests of engine use the same HTTP configuration (it was not the case before, see proxy configuration in master)