Skip to content

docs(settings): jmap_websocket_timeout #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0kaba0hub merged 1 commit into from
Oct 24, 2026
Merged

docs(settings): jmap_websocket_timeout #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions data/settings.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2154,6 +2154,20 @@ protocol.jmap.jmap_push_poll:
Interval between a push stream's looks for changes; `0` turns push off.
See [Push](#push).

protocol.jmap.jmap_websocket_timeout:
type: integer
unit: seconds
default: 1800
helm: protocol.jmap.jmap_websocket_timeout
added: 2.4.5
see_also: [protocol.jmap.jmap_push_poll]
description: |
How long a JMAP WebSocket may go without answering a ping before it is
closed. The server pings every half of it, so a live client keeps its
connection even when it only listens. `0` turns WebSocket off: the session
does not advertise it and the endpoint answers `404`. See
[WebSocket](/protocols/jmap#websocket).

protocol.jmap.jmap_cors_allow_origins:
type: list
default: []
Expand Down
Loading