Mercurial > prosody-modules
view mod_jid_prep/mod_jid_prep.lua @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parents | 99cb06b31ae8 |
children |
line wrap: on
line source
-- Run JIDs through stringprep processing on behalf of clients -- http://xmpp.org/extensions/inbox/jidprep.html local jid_prep = require "util.jid".prep; local st = require "util.stanza"; local xmlns_prep = "urn:xmpp:jidprep:0"; module:add_feature(xmlns_prep); function prep_jid(event) local stanza = event.stanza; local jid = jid_prep(stanza:get_child_text("jid", xmlns_prep)); if not jid then return event.origin.send(st.error_reply(stanza, "modify", "jid-malformed")); end return event.origin.send(st.reply(stanza):tag("jid", { xmlns = xmlns_prep }):text(jid)); end module:hook("iq/host/"..xmlns_prep..":jid", prep_jid); module:depends("http"); module:provides("http", { route = { ["GET /*"] = function (event, jid) return jid_prep(jid) or 400; end; } });