Skip to content
Commits on Feb 1, 2016
Commits on Jan 7, 2016
  1. New security feature: Redis protected mode.

    An exposed Redis instance on the internet can be cause of serious
    issues. Since Redis, by default, binds to all the interfaces, it is easy
    to forget an instance without any protection layer, for error.
    Protected mode try to address this feature in a soft way, providing a
    layer of protection, but giving clues to Redis users about why the
    server is not accepting connections.
    When protected mode is enabeld (the default), and if there are no
    minumum hints about the fact the server is properly configured (no
    "bind" directive is used in order to restrict the server to certain
    interfaces, nor a password is set), clients connecting from external
    intefaces are refused with an error explaining what to do in order to
    fix the issue.
    Clients connecting from the IPv4 and IPv6 lookback interfaces are still
    accepted normally, similarly Unix domain socket connections are not
    restricted in any way.
Commits on Dec 3, 2015
Commits on Oct 15, 2015
Commits on Oct 5, 2015
Commits on Apr 27, 2015
Commits on Apr 26, 2015
  1. Example redis.conf doc about pidfile fixed.

    An user changed the behavior via a PR without upgrading the doc.
Commits on Feb 19, 2015
  1. Example redis.conf binds just to

    It's hard to pick a good approach here. A few arguments:
    1) There are many exposed instances on the internet.
    2) Changing the default when "bind" is not given is very dangerous,
       after an upgrade the server changes a fundamental behavior.
    3) Usually Redis, when used in a proper way, will be protected *and*
       accessed often from other computers, so this new default is likely
       not what most people want.
    4) However if users end with this default, they are using the example
       redis.conf: likely they are reading what is inside, and they'll see
       the warning.
Commits on Jan 8, 2015
Commits on Dec 11, 2014
  1. Merge pull request #2117 from mariano-perez-rodriguez/patch-4

    Typo fixes in redis.conf
Commits on Dec 2, 2014
Commits on Oct 27, 2014
Commits on Oct 24, 2014
Commits on Sep 17, 2014
Commits on Sep 8, 2014
Commits on Jul 25, 2014
Commits on Jul 2, 2014
  1. Latency monitor trheshold value is now configurable.

    This commit adds both support for redis.conf and CONFIG SET/GET.
Commits on Jun 16, 2014
  1. Client types generalized.

    Because of output buffer limits Redis internals had this idea of type of
    clients: normal, pubsub, slave. It is possible to set different output
    buffer limits for the three kinds of clients.
    However all the macros and API were named after output buffer limit
    classes, while the idea of a client type is a generic one that can be
    This commit does two things:
    1) Rename the API and defines with more general names.
    2) Change the class of clients executing the MONITOR command from "slave"
       to "normal".
    "2" is a good idea because you want to have very special settings for
    slaves, that are not a good idea for MONITOR clients that are instead
    normal clients even if they are conceptually slave-alike (since it is a
    push protocol).
    The backward-compatibility breakage resulting from "2" is considered to
    be minimal to care, since MONITOR is a debugging command, and because
    anyway this change is not going to break the format or the behavior, but
    just when a connection is closed on big output buffer issues.
Commits on May 22, 2014
  1. Cluster: slave validity factor is now user configurable.

    Check the commit changes in the example redis.conf for more information.
Commits on Apr 15, 2014
Commits on Mar 21, 2014
  1. The default maxmemory policy is now noeviction.

    This is safer as by default maxmemory should just set a memory limit
    without any key to be deleted, unless the policy is set to something
    more relaxed.
Commits on Mar 20, 2014
  1. Default LRU samples is now 5.

Commits on Jan 31, 2014
  1. Option "backlog" renamed "tcp-backlog".

    This is especially important since we already have a concept of backlog
    (the replication backlog).
  2. Cluster: configurable replicas migration barrier.

    It is possible to configure the min number of additional working slaves
    a master should be left with, for a slave to migrate to an orphaned
Commits on Dec 19, 2013
Commits on Dec 6, 2013
  1. Fixed typo in redis.conf.

Commits on Dec 5, 2013
Commits on Oct 9, 2013
Commits on Jul 8, 2013
  1. Revert "Document port6 and bind6 config options."

    IPv6 support is not going to use IPv6 specific options, just it will be
    possible to specify all the ipv4 / ipv6 addresses of the interfaces to
    bind, otherwise connections will be accepted from all the interfaces in
    both IPv4 and IPv6 addresses.
    This reverts commit 93570e1.
Something went wrong with that request. Please try again.