Redis Escape & Unescape

It depends on the context. In redis-cli double-quoted strings, escape double quotes (\"), backslashes (\\), and control characters (\n, \r, \t). In connection string URLs, encode @, #, :, and / using percent-encoding (%40, %23, %3A, %2F). In KEYS/SCAN glob patterns, escape *, ?, [, and ] with backslash for literal matching. Client libraries handle RESP protocol escaping automatically.

Yes, Redis keys are binary safe and can contain any bytes, including spaces, newlines, and null bytes. However, for maintainability, avoid very long keys (>1KB) and prefer readable patterns like user:1234:profile. The colon (:) is a common namespace separator.

RediSearch uses its own query syntax where characters like @, !, {, }, (, ), -, ~, and * have special meaning. Escape them with a backslash: FT.SEARCH idx "hello\-world". For exact phrases, wrap in double quotes. Note that RediSearch escaping is different from redis-cli escaping - RediSearch operates at the query parser level, not the protocol level.

In redis-cli, use: redis-cli -a 'password@with#special' (single quotes protect most characters). In connection strings, URL-encode special characters: @ becomes %40, # becomes %23, : becomes %3A. Our connection string generator handles this automatically.

In redis-cli with double-quoted strings, escape double quotes with backslash: SET key "value with \"quotes\"". Single quotes don't need escaping inside double quotes. In most programming languages, the Redis client library handles escaping automatically.