view mod_migrate_http_upload/README.md @ 6411:b00638d74f46

mod_unified_push: Allow additional CORS headers for unified push (fixes #1985) - Request header "TTL" is mandated by the HTTP Push specification RFC 8030: https://datatracker.ietf.org/doc/html/rfc8030#section-5 - Firefox sends "Content-Encoding" with a HTTP form submission, so it is required when using the Unified Push testing tool at https://unifiedpush.org/test_wp.html (with the full URL being delivered by the UP-Example Android app) Adding both headers makes the Unified Push testing tool work from the browser. Resolves: https://issues.prosody.im/1985
author Christian Weiske <cweiske@cweiske.de>
date Sat, 21 Feb 2026 19:13:08 +0100
parents fe081789f7b5
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"
}
```