KamoCRM

Stop renewing the shared *** TTL for idle users

FixDocsService
Ya
9 Agosti 2026, 19:59 UTC
Mwandishi
Kamo
Ahadi ya
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.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei