prosody-modules
fe8222112cf4
mod_firewall/scripts/spam-blocklists.pfw
Software / code / prosody-modules
File
mod_firewall/scripts/spam-blocklists.pfw @ 6199:fe8222112cf4
mod_conversejs: Serve base app at /
This makes things slightly less awkward for the browser to figure out which
URLs belong to a PWA. The app's "start URL" was previously without the '/' and
therefore was not considered within the scope of the PWA. Now the canonical
app URL will always have a '/'.
Prosody/mod_http should take care of redirecting existing links without the
trailing / to the new URL.
If you have an installation at https://prosody/conversejs then it is now at
https://prosody/conversejs/ (the first URL will now redirect to the second
URL if you use it).
The alternative would be to make the PWA scope include the parent, i.e.
the whole of https://prosody/ in this case. This might get messy if other
PWAs are provided by the same site or Prosody installation, however.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 11 Feb 2025 13:18:38 +0000 |
| parent | 5532:d84757f9adcb |
line wrap: on
line source
# This script depends on spam-blocking.pfw also being loaded # Any traffic that is not explicitly blocked or allowed by other # rules will be checked against the JabberSPAM server blocklist %LIST blocklist: https://cdn.jsdelivr.net/gh/jabberspam/blacklist/blacklist.txt ::user/spam_handle_unknown_custom CHECK LIST: blocklist contains $<@from|host> BOUNCE=policy-violation (Your server is blocked due to spam) ::user/spam_check_muc_invite_custom # Check the server we received the invitation from CHECK LIST: blocklist contains $<@from|host> BOUNCE=policy-violation (Your server is blocked due to spam) # Check the inviter's JID against the blocklist, too CHECK LIST: blocklist contains $<{http://jabber.org/protocol/muc#user}x/invite@from|host> BOUNCE=policy-violation (Your server is blocked due to spam)
