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.

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

This module attempts to sanitize XHTML-IM messages.

It does **not** attempt to sanitize any CSS embedded in `style`
attributes, these are instead stripped by default.

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

  Option                   Type      Default
  ------------------------ --------- ---------
  `strip_xhtml_style`      boolean   `true`
  `bounce_invalid_xhtml`   boolean   `false`