zeripath 71aa64ae25 fix broken insecureskipverify handling in rediss connection uris (#20967) (#21053) ... Backport #20967 Currently, it's impossible to connect to self-signed TLS encrypted redis instances. The problem lies in inproper error handling, when building redis tls options - only invalid booleans are allowed to be used in `tlsConfig` builder. The problem is, when `strconv.ParseBool(...)` returns error, it always defaults to false - meaning it's impossible to set `tlsOptions.InsecureSkipVerify` to true. Fixes #19213 Co-authored-by: Igor Rzegocki <ajgon@users.noreply.github.com>		2022-09-04 14:59:20 +01:00
..
leveldb.go	Allow common redis and leveldb connections (#12385)	2020-09-28 00:09:46 +03:00
manager.go	Remove legacy `unknwon/com` package (#19298)	2022-04-02 00:34:57 +08:00
manager_leveldb.go	Add Goroutine stack inspector to admin/monitor (#19207)	2022-03-31 19:01:43 +02:00
manager_redis.go	fix broken insecureskipverify handling in rediss connection uris (#20967) (#21053)	2022-09-04 14:59:20 +01:00
manager_redis_test.go	fix broken insecureskipverify handling in rediss connection uris (#20967) (#21053)	2022-09-04 14:59:20 +01:00
redis.go	format with gofumpt (#18184)	2022-01-20 18:46:10 +01:00
redis_test.go	Allow common redis and leveldb connections (#12385)	2020-09-28 00:09:46 +03:00