Software /
code /
prosody-modules
File
mod_isolate_host/README.md @ 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 | 6003:fe081789f7b5 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Prevent communication between hosts ... Introduction ============ In some environments it is desirable to isolate one or more hosts, and prevent communication with external, or even other internal domains. Loading mod\_isolate\_host on a host will prevent all communication with JIDs outside of the current domain, though it is possible to configure exceptions. **Note:** if you just want to prevent communication with external domains, this is possible without a plugin. See [Prosody: Disabling s2s](http://prosody.im/doc/s2s#disabling) for more information. This module was sponsored by [Exa Networks](http://exa-networks.co.uk/). Configuration ============= To isolate all hosts by default, add the module to your global modules\_enabled: ``` {.lua} modules_enabled = { ... "isolate_host"; ... } ``` Alternatively you can isolate a single host by putting a modules\_enabled line under the VirtualHost directive: ``` {.lua} VirtualHost "example.com" modules_enabled = { "isolate_host" } ``` After enabling the module, you can add further options to add exceptions for the isolation: Option Description -------------------------- ----------------------------------------------------------------------------------------- isolate\_except\_domains A list of domains to allow communication with. isolate\_except\_users A list of user JIDs allowed to bypass the isolation and communicate with other domains. **Note:** Admins of hosts are always allowed to communicate with other domains Compatibility ============= ----- ------- 0.9 Works ----- -------