- 30 Mar, 2021 1 commit
-
-
Viktor Söderqvist authored
The cluster bus is established over TLS or non-TLS depending on the configuration tls-cluster. The client ports distributed in the cluster and sent to clients are assumed to be TLS or non-TLS also depending on tls-cluster. The cluster bus is now extended to also contain the non-TLS port of clients in a TLS cluster, when available. The non-TLS port of a cluster node, when available, is sent to clients connected without TLS in responses to CLUSTER SLOTS, CLUSTER NODES, CLUSTER SLAVES and MOVED and ASK redirects, instead of the TLS port. The user was able to override the client port by defining cluster-announce-port. Now cluster-announce-tls-port is added, so the user can define an alternative announce port for both TLS and non-TLS clients. Fixes #8134
-
- 21 Feb, 2021 1 commit
-
-
Huang Zw authored
When redis responds with tracking-redir-broken push message (RESP3), it was responding with a broken protocol: an array of 3 elements, but only pushes 2 elements. Some bugs in the test make this pass. Read the push reply will consume an extra reply, because the reply length is 3, but there are only two elements, so the next reply will be treated as third element. So the test is corrected too. Other changes: * checkPrefixCollisionsOrReply success should return 1 instead of -1, this bug didn't have any implications. * improve client tracking tests to validate more of the response it reads.
-
- 26 Jan, 2021 1 commit
-
-
Oran Agra authored
It was confusing as to why these don't return a map type. the reason is that order matters, so we need to make sure the client library knows to respect it. Added comments in the implementation and tests to cover it.
-
- 05 Jan, 2021 1 commit
-
-
Oran Agra authored
When a Lua script returns a map to redis (a feature which was added in redis 6 together with RESP3), it would have returned the value first and the key second. If the client was using RESP2, it was getting them out of order, and if the client was in RESP3, it was getting a map of value => key. This was happening regardless of the Lua script using redis.setresp(3) or not. This also affects a case where the script was returning a map which it got from from redis by doing something like: redis.setresp(3); return redis.call() This fix is a breaking change for redis 6.0 users who happened to rely on the wrong order (either ones that used redis.setresp(3), or ones that returned a map explicitly). This commit also includes other two changes in the tests: 1. The test suite now handles RESP3 maps as dicts rather than nested lists 2. Remove some redundant (duplicate) tests from tracking.tcl
-
- 11 Dec, 2020 1 commit
-
-
Yossi Gottlieb authored
This adds a new `tls-client-cert-file` and `tls-client-key-file` configuration directives which make it possible to use different certificates for the TLS-server and TLS-client functions of Redis. This is an optional directive. If it is not specified the `tls-cert-file` and `tls-key-file` directives are used for TLS client functions as well. Also, `utils/gen-test-certs.sh` now creates additional server-only and client-only certs and will skip intensive operations if target files already exist.
-
- 06 Dec, 2020 1 commit
-
-
Oran Agra authored
when using --baseport to run two tests suite in parallel (different folders), we need to also make sure the port used by the testsuite to communicate with it's workers is unique. otherwise the attept to find a free port connects to the other test suite and messes it. maybe one day we need to attempt to bind, instead of connect when tring to find a free port.
-
- 09 Nov, 2020 1 commit
-
-
nitaicaro authored
Test support for the new map, null and push message types. Map objects are parsed as a list of lists of key value pairs. for instance: user => john password => 123 will be parsed to the following TCL list: {{user john} {password 123}} Also added the following tests: Redirection still works with RESP3 Able to use a RESP3 client as a redirection client No duplicate invalidation messages when turning BCAST mode on after normal tracking Server is able to evacuate enough keys when num of keys surpasses limit by more than defined initial effort Different clients using different protocols can track the same key OPTOUT tests OPTIN tests Clients can redirect to the same connection tracking-redir-broken test HELLO 3 checks Invalidation messages still work when using RESP3, with and without redirection Switching to RESP3 doesn't disturb previous tracked keys Tracking info is correct Flushall and flushdb produce invalidation messages These tests achieve 100% line coverage for tracking.c using lcov.
-
- 07 Oct, 2019 2 commits
-
-
Yossi Gottlieb authored
Add configuration options for TLS protocol versions, ciphers/cipher suites selection, etc.
-
Yossi Gottlieb authored
* Introduce a connection abstraction layer for all socket operations and integrate it across the code base. * Provide an optional TLS connections implementation based on OpenSSL. * Pull a newer version of hiredis with TLS support. * Tests, redis-cli updates for TLS support.
-
- 29 Sep, 2014 1 commit
-
-
Matt Stancliff authored
-
- 18 Jun, 2014 2 commits
- 13 May, 2014 1 commit
-
-
antirez authored
-
- 30 Apr, 2014 1 commit
-
-
antirez authored
-
- 30 May, 2013 1 commit
-
-
antirez authored
-
- 06 Apr, 2012 1 commit
-
-
antirez authored
-
- 20 Mar, 2012 1 commit
-
-
antirez authored
DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and other commands against read only slaves.
-
- 15 Oct, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 13 Oct, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 16 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 15 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 11 Jun, 2010 1 commit
-
-
Robey Pointer authored
-
- 14 May, 2010 2 commits
-
-
antirez authored
-
Pieter Noordhuis authored
-
- 23 Apr, 2010 1 commit
-
-
antirez authored
-
- 19 Apr, 2010 1 commit
-
-
antirez authored
Added package require Tcl 8.5 in redis.tcl so it will show a clear error when the test suit is attempted to run under 8.4
-
- 15 Apr, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 12 Apr, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 08 Apr, 2010 1 commit
-
-
antirez authored
-
- 07 Apr, 2010 1 commit
-
-
antirez authored
-
- 17 Mar, 2010 1 commit
-
-
antirez authored
-
- 15 Mar, 2010 3 commits
- 04 Feb, 2010 1 commit
-
-
antirez authored
-
- 22 Jan, 2010 1 commit
-
-
antirez authored
-
- 21 Nov, 2009 1 commit
-
-
antirez authored
-
- 20 Nov, 2009 1 commit
-
-
antirez authored
-
- 03 Nov, 2009 1 commit
-
-
antirez authored
-