mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

---
labels:
- 'Stage-Stable'
summary: 'Close idle server-to-server connections'
...

Introduction
============

Some people find it preferable to close server-to-server connections
after they have been silent for a while.

Configuration
=============

...is trivial. The default timeout is 300 seconds (5 minutes). To change
this simply put in the config:

       s2s_idle_timeout = 60 -- or any other number of seconds

Compatibility
=============

  ----- -------
  0.6   Works
  0.7   Works
  ----- -------