Mercurial > prosody-modules
view mod_migrate_http_upload/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 (24 months ago) |
parents | 6844733ad2f5 |
children |
line wrap: on
line source
--- summary: mod_http_upload to mod_http_file_share migrator labels: - Stage-Alpha --- This is a migration script for converting records of [mod_http_upload] into the format used by the new [mod_http_file_share][doc:modules:mod_http_file_share] which will be available with Prosody 0.12 (currently in trunk). # Usage If your main `VirtualHost` is called "example.com" and your HTTP upload `Component` is called "upload.example.com", then this command would convert records of existing uploads via [mod_http_upload] to [mod_http_file_share][doc:modules:mod_http_file_share]: ```bash sudo prosodyctl mod_migrate_http_upload upload.example.com example.com ``` In order to preserve URLs you will need to configure the [path][doc:http#path_configuration] to be the same as mod_http_upload: ```lua Component "upload.example.com" "http_file_share" http_paths = { file_share = "/upload" } ```