mod_http_upload
Module Description
This module implements XEP-0363: HTTP File Upload, version 0.3.0+.
It enables a service that on user request creates an upload "slot".
A slot is a pair of URLs, one of which can be used with a PUT
method to upload a user's file, the other with a GET
method to retrieve such file.
Currently, the module supports only the S3 backend using AWS Signature Version 4.
Options
modules.mod_http_upload.iqdisc.type
- Syntax: string, one of
"one_queue"
,"no_queue"
,"queues"
,"parallel"
- Default:
"one_queue"
Strategy to handle incoming stanzas. For details, please refer to IQ processing policies.
modules.mod_http_upload.host
- Syntax: string
- Default:
"upload.@HOST@"
- Example:
host = "upload.@HOST@"
Subdomain for the upload service to reside under. @HOST@
is replaced with each served domain.
modules.mod_http_upload.backend
- Syntax: non-empty string
- Default:
"s3"
- Example:
backend = "s3"
Backend to use for generating slots. Currently only "s3"
can be used.
modules.mod_http_upload.expiration_time
- Syntax: positive integer
- Default:
60
- Example:
expiration_time = 120
Duration (in seconds) after which the generated PUT
URL will become invalid.
modules.mod_http_upload.token_bytes
- Syntax: positive integer
- Default:
32
- Example:
token_bytes = 32
Number of random bytes of a token that will be used in a generated URL. The text representation of the token will be twice as long as the number of bytes, e.g. for the default value the token in the URL will be 64 characters long.
modules.mod_http_upload.max_file_size
- Syntax: positive integer
- Default: not set - no size limit
- Example:
max_file_size = 10485760
Maximum file size (in bytes) accepted by the module.
modules.mod_http_upload.s3
- Syntax: Array of TOML tables. See description.
- Default: see description
- Example: see description
Options specific to S3 backend.
Note
This section is mandatory.
S3 backend options
s3.bucket_url
- Syntax: non-empty string
- Default: none, this option is mandatory
- Example:
s3.bucket_url = "https://s3-eu-west-1.amazonaws.com/mybucket"
A complete URL pointing at the used bucket. The URL may be in virtual host form, and for AWS it needs to point to a specific regional endpoint for the bucket. The scheme, port and path specified in the URL will be used to create PUT
URLs for slots, e.g. specifying a value of "https://s3-eu-west-1.amazonaws.com/mybucket/custom/prefix"
will result in PUT
URLs of form "https://s3-eu-west-1.amazonaws.com/mybucket/custom/prefix/<RANDOM_TOKEN>/<FILENAME>?<AUTHENTICATION_PARAMETERS>"
.
s3.add_acl
- Syntax: boolean
- Default:
false
- Example:
s3.add_acl = true
If true
, adds x-amz-acl: public-read
header to the PUT URL.
This allows users to read the uploaded files even if the bucket is private. The same header must be added to the PUT request.
s3.region
- Syntax: string
- Default:
""
, this option is mandatory - Example:
s3.region = "https://s3-eu-west-1.amazonaws.com/mybucket"
The AWS region to use for requests.
s3.access_key_id
- Syntax: string
- Default:
""
, this option is mandatory - Example:
s3.access_key_id = "AKIAIOSFODNN7EXAMPLE"
ID of the access key to use for authorization.
s3.secret_access_key
- Syntax: string
- Default:
""
, this option is mandatory - Example:
s3.secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
Secret access key to use for authorization.
Example configuration
1 2 3 4 5 6 7 8 9 |
|
Testing S3 configuration
Since there is no direct connection between MongooseIM and an S3 bucket,
it is not possible to verify the provided S3 credentials during startup.
However, the testing can be done manually. MongooseIM provides a dedicated mongooseimctl httpUpload getUrl
command for the manual URLs generation. It requires the following arguments:
- domain - XMPP host name.
- filename - Name of the file.
- size - Size of the file in bytes (positive integer).
- contentType - Content-Type.
- timeout - Duration (in seconds, positive integer) after which the generated
PUT
URL will become invalid. This argument shadows the expiration_time configuration.
The generated URLs can be used to upload/download a file using the curl
utility:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
|
Using S3 backend with min.io
min.io doesn't support ObjectACL, so enabling add_acl
makes no sense. The bucket policies must be used instead,
it is enough to set the bucket policy to download
.
Please note that there is no error if you keep add_acl
enabled. min.io just
ignores the x-amz-acl
header. This might be useful to simplify the migration from S3
to min.io
Metrics
If you'd like to learn more about metrics in MongooseIM, please visit MongooseIM metrics page.
Backend action | Description (when it gets incremented) |
---|---|
create_slot |
An upload slot is allocated. |