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.

---
summary: Allow specified JIDs to bypass rate limits
...

This module allows you to configure a list of JIDs that should be allowed to
bypass rate limit restrictions.

It is designed for Prosody 0.11.x. Prosody 0.12.x supports this feature
natively.

## Configuration

First, enable this module by adding `"limits_exception"` to your
`modules_enabled` list.

Next, configure a list of JIDs to exclude from rate limiting:

```
unlimited_jids = { "user1@example.com", "user2@example.net" }
```

## Compatibility

Made for Prosody 0.11.x only.

Using this module with Prosody trunk/0.12 may cause unexpected behaviour.