Mercurial > prosody-modules
view mod_muc_config_restrict/README.markdown @ 4931:13070c6a7ce8
mod_http_muc_log: Fix exception on lack of trailing slash in room path
A request to /room leads to the match call returning nil which in turn
calls nodeprep(nil). In Prosody 0.11.x this does nothing and simply
returns the nil, while in 0.12 it is an error.
Now it redirects to the calendar view at /room/ - even for non-existant
rooms.
Discovered at a deployment with http_paths = { muc_log = "/" } and
requests to /robots.txt and similar, which now result in a uses redirect
before returning 404.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 22 Apr 2022 14:29:32 +0200 |
parents | 8de50be756e5 |
children | 34fb3d239ac1 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Restrict MUC configuration options to server admins ... Introduction ============ Sometimes, especially on public services, you may want to allow people to create their own rooms, but prevent some options from being modified by normal users. For example, using this module you can prevent users from making rooms persistent, or making rooms publicly visible. Details ======= You need to supply a list of options that will be restricted to admins. Available options can vary, but the following table lists Prosody's built-in options (as defined in XEP-0045): Name Description --------------------------------- ------------------------------------------- muc\#roomconfig\_roomname The title/name of the room muc\#roomconfig\_roomdesc The description of the room muc\#roomconfig\_persistentroom Whether the room should remain when empty muc\#roomconfig\_publicroom Whether the room is publicly visible muc\#roomconfig\_changesubject Whether occupants can change the subject muc\#roomconfig\_whois Control who can see occupant's real JIDs muc\#roomconfig\_roomsecret The room password muc\#roomconfig\_moderatedroom Whether the room is moderated muc\#roomconfig\_membersonly Whether the room is members-only muc\#roomconfig\_historylength The length of the room history Some plugins may add other options to the room config (in Prosody 0.10+), for which you will need to consult their documentation for the full option name. Configuration ============= Enable the plugin on a MUC host (do not put it in your global modules\_enabled list): ``` {.lua} Component "conference.example.com" "muc" modules_enabled = { "muc_config_restrict" } muc_config_restricted = { "muc#roomconfig_persistentroom"; -- Prevent non-admins from changing a room's persistence setting "muc#roomconfig_membersonly"; -- Prevent non-admins from changing whether rooms are members-only } ``` Compatibility ============= ------- -------------- trunk Works 0.9 Doesn't work 0.8 Doesn't work ------- --------------