Mercurial > prosody-modules
view mod_storage_multi/README.markdown @ 5285:8e1f1eb00b58
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.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Wed, 29 Mar 2023 16:12:15 +0100 |
parents | a7fdab9c14e2 |
children |
line wrap: on
line source
--- summary: Multi-backend storage module (WIP) labels: - NeedDocs - Stage-Alpha ... Introduction ============ This module attemtps to provide a storage driver that is really multiple storage drivers. This could be used for storage error tolerance or caching of data in a faster storage driver. Configuration ============= An example: ``` {.lua} storage = "multi" storage_multi_policy = "all" storage_multi = { "memory", "internal", "sql" } ``` Here data would be first read from or written to [mod\_storage\_memory], then internal storage, then SQL storage. For reads, the first successful read will be used. For writes, it depends on the `storage_multi_policy` option. If set to `"all"`, then all storage backends must report success for the write to be considered successful. Other options are `"one"` and `"majority"`.