Support rediss:// protocol to connect to redis over TLS

Description

Kutt currently lacks support for connecting to Redis using the rediss:// protocol, which is necessary for establishing encrypted TLS connections. This limitation hinders secure deployments where Redis communication must be encrypted in transit to meet organizational security policies or compliance standards.

Enhancement Proposal

Add support for the rediss:// URI scheme in Kutt's Redis connection logic to enable secure TLS communication with Redis servers. The implementation should ensure compatibility with existing Redis TLS configurations and environment variables.

Rationale

• Improves security by enabling encrypted communication with the Redis backend.
• Facilitates deployments in environments that enforce TLS for all service traffic.
• Aligns with modern best practices for protecting data in transit.

Default Ports for Redis

Protocol	Port	Description
redis://	6379	Default plaintext Redis connection
rediss://	6380	Common port used for TLS connections

Related Work

• #718

---

Let me know if you'd like to add a configuration example, validation logic, or notes about fallbacks. Happy to tweak further!