Memcache Plugin

This plugin implements the memcache protocol for cache contents.

重要

This plugin exposes the shared Traffic Server cache with no authentication or access control. Read Security before deploying it, and in particular before binding it to any non-loopback address.

インストール

次の行を plugin.config に追加してください。

tsmemcache.so 11211

このケースでは、プラグインはデフォルトの振る舞いをします

  • Listen for memcache traffic on the default memcache port 11211

  • Bind only to the loopback address (127.0.0.1), so the listener is not reachable from other hosts on the network

  • Write memcache data to the cache in the background (without waiting)

To bind the listener to a specific address, pass it as a second argument:

tsmemcache.so 11211 127.0.0.1

See Security before binding to any non-loopback address.

設定

もしくは、設定を指定することも可能です。

tsmemcache.so <path-to-plugin>/sample.tsmemcache.config

After modifying plugin.config, restart Traffic Server (sudo traffic_ctl server restart) the configuration is also re-read when a management update is given (sudo traffic_ctl config reload)

オプション

フラグとオプションは次のとおりです。

port: A single port to listen on for memcache protocol commands.

bind_ip: Optional. The local IP address to bind the listener to. Defaults to 127.0.0.1 (loopback only). Specifying a non-loopback address (for example 0.0.0.0 or a specific interface address) deliberately exposes the listener to the network; see Security.

Options in the code: TSMEMCACHE_WRITE_SYNC whether or not to wait for the write to complete.

Security

重要

The tsmemcache plugin operates directly on the shared Traffic Server object cache: any client that can reach the listener can read, overwrite, and delete cache entries, including content served by the HTTP proxy. The plugin performs no authentication (the binary protocol's SASL commands are not implemented) and applies no ip_allow.yaml ACL on its accept path -- those controls exist only on the HTTP/2/3 session-accept paths, which this plugin does not use.

For this reason the listener binds to the loopback address (127.0.0.1) by default, so it is not reachable from the network. Only bind to a non-loopback address if the port is otherwise protected (for example by a host or network firewall that restricts access to trusted clients). When a non-loopback address is configured the plugin logs a warning at startup, and an invalid bind address causes the plugin to fail to load rather than silently fall back to a wildcard bind.