Server settings
Advanced
HTTP cache TTLs and webhook delivery guards — sharp-edged knobs.
HTTP cache
A built-in shared cache sits in front of read-heavy endpoints. Entries are keyed per access context — private content never leaks across viewers — and mutations purge affected pages immediately.
httpCachePageTtlSeconds seconds default 0 = offMessage-history pages and other cached read surfaces. Short TTLs already absorb most read load.
httpCachePresenceTtlSeconds secondsPresence summaries — TTL-only (no purging); the client polls every 30s, so ~15s is a good value.
Webhooks
webhookMaxQueued integerCap on buffered deliveries while an endpoint is down; overflow drops oldest.
webhookLogRetentionDays daysHow long delivery attempts stay inspectable in the admin panel.
webhookAllowInternalUrls boolean default falseSSRF guard — enable only to deliberately target services on the server’s own network.