view mod_migrate_http_upload/README.markdown @ 5796:93d6e9026c1b

mod_http_oauth2: Do not enforce PKCE on Device and OOB flows PKCE does not appear to be used with the Device flow. I have found no mention of any interaction between those standards. Since no data is delivered via redirects in these cases, PKCE may not serve any purpose. This is mostly a problem because we reuse the authorization code to implement the Device and OOB flows.
author Kim Alvefur <zash@zash.se>
date Fri, 15 Dec 2023 12:10:07 +0100
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"
}
```