Kim Alvefur <zash@zash.se> [Tue, 22 Nov 2022 23:56:01 +0100] rev 12801
util.stanza: Allow U+7F
Allowed by XML despite arguably being a control character.
Drops the part of the range meant to rule out octets invalid in UTF-8
(\247 starts a 4-byte sequence), since UTF-8 correctness is validated by
util.encodings.utf8.valid().
Kim Alvefur <zash@zash.se> [Sun, 13 Nov 2022 18:16:59 +0100] rev 12800
mod_smacks: Disable resumption behavior on s2s
Since resumption is not supported on s2s currently, there is no point in
allocating resumption tokens. The code that removes entries from
session_registry is only invoked for c2s sessions, thus enabling
resumable smacks on s2s adds an entry that never goes away.
Matthew Wild <mwild1@gmail.com> [Fri, 02 Dec 2022 20:32:36 +0000] rev 12799
util.hashring: Support associating arbitrary data with nodes
In this API, a 'node' is always a simple text string. Sometimes the caller may
have a more complex structure representing a node, but the hash ring is really
only concerned with the node's name.
This API change allows :add_nodes() to take a table of `node_name = value`
pairs, as well as the simple array of node names previously accepted.
The 'value' of the selected node is returned as a new second result from
:get_node().
If no value is passed when a node is added, it defaults to `true` (as before,
but this was never previously exposed).
Matthew Wild <mwild1@gmail.com> [Fri, 02 Dec 2022 20:27:32 +0000] rev 12798
util.hashring: tests: don't randomize order - they are written in a sequential style
Matthew Wild <mwild1@gmail.com> [Fri, 04 Nov 2022 12:26:43 +0000] rev 12797
Merge 0.12->trunk
Matthew Wild <mwild1@gmail.com> [Fri, 04 Nov 2022 12:26:10 +0000] rev 12796
util.json: Accept empty arrays with whitespace (fixes #1782)
Matthew Wild <mwild1@gmail.com> [Mon, 31 Oct 2022 14:32:26 +0000] rev 12795
Merge 0.12->trunk
Matthew Wild <mwild1@gmail.com> [Mon, 31 Oct 2022 14:32:02 +0000] rev 12794
mod_http: Allow disabling CORS in the http_cors_override option and by default
Fixes #1779.
Due to an oversight in the logic, if the user set 'enabled' to false in an
override, it would disable the item's requested CORS settings, but still apply
Prosody's default CORS policy.
This change ensures that 'enabled = false' will now disable CORS entirely for
the requested item.
Due to the new structure of the code, it was necessary to have a flag to say
whether CORS is to be applied at all. Rather than hard-coding 'true' here, I
chose to add a new option: 'http_default_cors_enabled'. This is a boolean that
allows the operator to disable Prosody's default CORS policy entirely (the one
that is used when a module or config does not override it). This makes it
easier to disable CORS and then selectively enable it only on services you
want it on.
Kim Alvefur <zash@zash.se> [Mon, 24 Oct 2022 15:25:12 +0200] rev 12793
Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Sun, 23 Oct 2022 16:22:12 +0200] rev 12792
mod_admin_shell: Ensure available connection for column 'secure'
Similar to #1777