#971 New default read timeout value

Reporter Zash
Owner Zash
Stars ★ (1)  
  • Status-Fixed
  • Type-Enhancement
  • Priority-Medium
  • Milestone-0.11
  1. Zash on

    The read timeout value defaults to 6 hours. This made sense back when a session was unconditionally terminated at the end of that time, less so in 0.10+ where the action can be determined by a plugin and defaults to sending a keepalive whitespace. We need to determine an appropriate value.

  2. ge0rg on

    That would be great, as it would also allow to make reasonable use of mod_smacks.handle_read_timeout() to check if a c2s session is still "alive". On my server, I've worked around that by applying this: network_settings = { read_timeout = 840; } This is 14 minutes, so it is intended to ping all c2s and s2s sessions before potential NAT timeouts on rather restrictive NAT gateways. Full context is in #712.

  3. Zash on

    It should be noted that this timeout applies to all connections, not just the xmpp connections, but http connections too. Without a listener callback, the default action is still to close the connection. The new default value should be chosen with this in mind. Currently (in 0.10) mod_c2s and mod_s2s provide a callback for this that fires the above mentioned event and whitespace-sending event handler.

  4. Zash on

    Changed in trunk http://hg.prosody.im/trunk/rev/23f66f04e216

    • owner Zash
    • tags Milestone-0.11 Status-Fixed

New comment

Not published. Used for spam prevention and optional update notifications.