client_max_body_size does not apply to HTTP

[frafra]

Hi :)
client_max_body_size works only when connecting to HTTPS, not when using HTTP (or doing HTTPS offloading in front of the service):

GSS/docker/https/nginx.conf

Line 55 in 9612721

client_max_body_size 1500M;

[moovida]

Yeah, should be removing that one anyway. Not yet sure how to handle large mapsforge files though.

[frafra]

The default client_max_body_size is 1M, which is rather small. It could help checking if compression is enabled.

There are different ways to handle very large file uploads.

Large files can be uploaded using TUS and/or S3 multipart uploads.

There is a client for DART and some support for Django, but they do not seem to be well maintained. We mostly use Uppy as an interface to upload data to a S3 storage via TUS, but using TUS in that scenario is entirely optional, since S3 supports multipart file uploads.