- 25 Feb, 2019 1 commit
-
-
antirez authored
-
- 13 Feb, 2019 2 commits
-
-
zhaozhao.zz authored
Adding another new filed categories at the end of command reply, it's easy to read and distinguish flags and categories, also compatible with old format.
-
antirez authored
That's not REALLY needed, but... right now with LASTSAVE being the only command tagged as "admin" but not "dangerous" what happens is that after rewrites the rewrite engine will produce from the rules: user default on +@all ~* -@dangerous nopass The rewrite: user default on nopass ~* +@all -@admin -@dangerous +lastsave Which is correct but will have users wondering about why LASTSAVE has something special. Since LASTSAVE after all also leaks information about the underlying server configuration, that may not be great for SAAS vendors, let's tag it as dangerous as well and forget about this issue :-)
-
- 12 Feb, 2019 1 commit
-
-
antirez authored
-
- 11 Feb, 2019 1 commit
-
-
antirez authored
The part that is fixed is that now if the default user is off whatever is its configuration the user is not considered authenticated.
-
- 07 Feb, 2019 1 commit
-
-
antirez authored
-
- 05 Feb, 2019 1 commit
-
-
antirez authored
-
- 04 Feb, 2019 1 commit
-
-
antirez authored
-
- 23 Jan, 2019 4 commits
- 22 Jan, 2019 4 commits
- 21 Jan, 2019 1 commit
-
-
antirez authored
-
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 17 Jan, 2019 2 commits
- 16 Jan, 2019 1 commit
-
-
antirez authored
-
- 15 Jan, 2019 3 commits
- 14 Jan, 2019 2 commits
- 11 Jan, 2019 2 commits
- 10 Jan, 2019 1 commit
-
-
antirez authored
-
- 09 Jan, 2019 11 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Because in RESP3 commands can be sent in the Pub/Sub connection without problems, so it's better if in such mode there is no exception about PING.
-
antirez authored
-
antirez authored
-
antirez authored
-