diff options
| author | Kim Alvefur <zash@zash.se> | 2023-09-16 14:23:08 +0200 |
|---|---|---|
| committer | Kim Alvefur <zash@zash.se> | 2023-09-16 14:23:08 +0200 |
| commit | df4bde023ba33f3a84538aa5cd10a0e1bda64990 (patch) | |
| tree | 821e1d23dddb6663618c930b4fd97d61ed6b7857 /plugins/mod_authz_internal.lua | |
| parent | eeaa713fda7927c885302b66f75ebe8b64531a01 (diff) | |
| download | prosody-df4bde023ba33f3a84538aa5cd10a0e1bda64990.tar.gz prosody-df4bde023ba33f3a84538aa5cd10a0e1bda64990.zip | |
mod_http_file_share: Switch to the new authz API (BC)
Behavior change: It becomes up to the authorization module whether to
allow requests. The default, mod_authz_internal, will allow users on the
*parent* host only, breaking use by some components.
Remaining question is whether to deprecate the `http_file_share_access`
setting or leave as a way to complement/bypass access control?
Diffstat (limited to 'plugins/mod_authz_internal.lua')
0 files changed, 0 insertions, 0 deletions