Repository navigation
Release v2.24.0
Summary
The idle limit AuthProxy applies to proxied requests, WebSocket sessions and Server-Sent Events streams is now configurable, and the documentation describes how streaming behaves through the proxy.
Added
ActivityTimeoutat the root (Cratis:AuthProxy:ActivityTimeout), per service underServicesand perBackend/Frontendendpoint; the most specific value wins and the default stays five minutes. Values must be between one millisecond and 2,147,483,647 milliseconds (about 24 days), inclusive; values outside this range stop AuthProxy at startup with a message naming the setting. (#153)- Unsupported activity timeout settings stop AuthProxy at startup with a message naming each setting:
Registration:ActivityTimeoutandActivityTimeoutonInvite:Lobbyor any of its endpoints. Remove these settings and configure the proxied service'sBackendorFrontendtimeout underServicesinstead. (#153) - Aspire
WithActivityTimeoutandWithServiceActivityTimeoutto set the limit from an app host. (#153) - Documentation of streaming through AuthProxy: heartbeats, interaction with platform idle limits, and when a stream is authorized. See Timeouts and streaming. (#153)