--- acl_categories: - '@slow' - '@connection' arguments: - arguments: - display_text: 'on' name: 'on' token: 'ON' type: pure-token - display_text: 'off' name: 'off' token: 'OFF' type: pure-token - display_text: skip name: skip token: SKIP type: pure-token name: action type: oneof arity: 3 categories: - docs - develop - stack - oss - rs - rc - oss - kubernetes - clients command_flags: - noscript - loading - stale complexity: O(1) description: Instructs the server whether to reply to commands. group: connection hidden: false linkTitle: CLIENT REPLY railroad_diagram: /images/railroad/client-reply.svg since: 3.2.0 summary: Instructs the server whether to reply to commands. syntax_fmt: CLIENT REPLY title: CLIENT REPLY --- Sometimes it can be useful for clients to completely disable replies from the Redis server. For example when the client sends fire and forget commands or performs a mass loading of data, or in caching contexts where new data is streamed constantly. In such contexts to use server time and bandwidth in order to send back replies to clients, which are going to be ignored, is considered wasteful. The `CLIENT REPLY` command controls whether the server will reply the client's commands. The following modes are available: * `ON`. This is the default mode in which the server returns a reply to every command. * `OFF`. In this mode the server will not reply to client commands. * `SKIP`. This mode skips the reply of command immediately after it. ## Redis Software and Redis Cloud compatibility | Redis
Software | Redis
Cloud | Notes | |:----------------------|:-----------------|:------| | ✅ Standard
✅ Active-Active | ✅ Standard
✅ Active-Active | | ## Return information {{< multitabs id="client-reply-return-info" tab1="RESP2" tab2="RESP3" >}} [Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK` when called with `ON`. When called with either `OFF` or `SKIP` sub-commands, no reply is made. -tab-sep- [Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK` when called with `ON`. When called with either `OFF` or `SKIP` sub-commands, no reply is made. {{< /multitabs >}}