File

mod_sasl2_fast: Restore non-FAST SASL handler upon reset This fixes an issue where, after failed FAST authentication, the FAST handler was still used (even though the client now wants to try with a password or other non-FAST credentials). A little hacky perhaps, but probably the best we can do without baking FAST support directly into mod_sasl2.

---
summary: Storage benchmark tool
...

To benchmark `mod_storage_internal`:

    prosodyctl mod_benchmark_storage internal

Does a number (aprox. 10000) of reads and writes and to the selected
storage driver and tells you how long it took.