KamoCRM

Stop renewing the shared *** TTL for idle users

FixDocsService
Shipped
9 ஆகஸ்ட், 2026 அன்று 7:59 PM UTC
Author
Kamo
Commit
8671608

Caught with redis MONITOR: this pod was issuing GET + PEXPIRE against a *** key whose owner had been idle for over an hour, seconds after SecurityService had correctly decoderd to renew it. This service keeps its own copy of KSessionService and slid the shared TTL on every read, so it kept sessions alive on its own. Honour X-Kamo-Idle-Ms as SecurityService, MediaService and ChatService now do. APIService relays every header except Host, so the signal already arrives. A caller that sends none still renews.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing