refactor(storage): enforce per-user max_file_bytes limit on upload pipelines (#20)
CD — Deployment / deploy (push) Successful in 22s

* Validate Content-Length on single-part upload route against user limit
* Check total expected size on chunked upload session creation
* Re-evaluate user limit at finalization to reject dynamic quota reductions
* Clean up temporary files on payload size rejection (413)
* Add 60-second polling interval for periodic fetching of messages and images

---------

Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #20
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
This commit was merged in pull request #20.
This commit is contained in:
Gitea Actions
2026-10-31 10:16:28 +00:00
committed by Esiah
co-authored by Esiah
parent b52417053f
commit 3542b33c89
12 changed files with 907 additions and 34 deletions
+5
View File
@@ -177,6 +177,11 @@ adresse ni aucun domaine n'est codé en dur.
de connexion globale, audit inutile).
- Certificat et HSTS sont assurés en amont par Cloudflare — ne pas exposer
directement le port 8083 sur Internet.
- **Corps de requête** : Cloudflare plafonne le corps à 100 MB (Free/Pro). Les
fichiers plus gros passent par l'envoi resumable (`/api/cloud/uploads`) en
morceaux de 50 MiB, sans relever la limite de corps de nginx ni exposer
l'origine. La valeur `client_max_body_size 5g` de nginx ne concerne que le
chemin direct local.
**Tunnel Docker sur un réseau partagé (recommandé).** On joint nginx au réseau
du tunnel plutôt que de publier un port : `cloudflared` résout `nginx` par nom,