Redis over TLS, and what the rediss scheme does not decide
A pasted rediss URL selects encryption without verification, because nothing in a URL says whose certificate to trust; verification stays an explicit choice.
6 posts
Key browsing by pattern, type-aware value views and INFO-backed live monitoring. Where it stops: No SQL, and none is pretended — the editor speaks commands here.
A pasted rediss URL selects encryption without verification, because nothing in a URL says whose certificate to trust; verification stays an explicit choice.
Health, performance, slow log and clients all derive from Redis introspection commands, while the table and index panels come back empty because Redis has neither.
Prefix groups come from a bounded cursor scan, so several per-row actions are hidden rather than offered against something no command can address.
There is no separate connection type and no per-server branch, so the version panel shows the compatibility level a server publishes, not its product release.
Because the rows are groupings from a bounded scan, the plan rules carry a sentence saying so, what a command may name instead, and how far the list reaches.
A Redis ACL user without the INFO grant connects and browses keys, while health, overview and performance raise a permission error and the connection test reports degraded.
We use cookies to analyse site traffic and improve your experience. See our Privacy Policy for details.