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 /CHANGES | |
| 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 'CHANGES')
| -rw-r--r-- | CHANGES | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -51,6 +51,7 @@ TRUNK - mod_blocklist: New option 'migrate_legacy_blocking' to disable migration from mod_privacy - Moved all modules into the Lua namespace `prosody.` - Forwarded header from RFC 7239 supported, disabled by default +- mod_http_file_share now uses roles framework, affecting access from e.g. components ## Removed |