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: S2S connection override
...

# Introduction

This module is similar to [mod\_srvinjection] but less of an hack.

# Configuration

``` lua
-- In the global section

modules_enabled = {
    --- your other modules
    "s2soutinjection";
}

-- targets must be IPs, not hostnames
s2s_connect_overrides = {
    -- This one will use the default port, 5269
    ["example.com"] = "1.2.3.4";

    -- To set a different port:
    ["another.example"] = { "127.0.0.1", 9999 };
}
```

# Compatibility

Requires 0.9.x or later. Tested on 0.12.0