Files
CoHaiSe-CLOUD/docker/nginx/snippets/proxy-api.conf
T
Gitea ActionsandEsiah 3542b33c89
CD — Deployment / deploy (push) Successful in 22s
refactor(storage): enforce per-user max_file_bytes limit on upload pipelines (#20)
* 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]>
2026-10-31 10:16:28 +00:00

23 lines
1.0 KiB
Plaintext

# Relay vers l'API. Resolver Docker declare pour resoudre le conteneur a la
# demande : nginx peut demarrer avant l'API et lui survit pendant un
# redemarrage.
resolver 127.0.0.11 valid=30s ipv6=off;
set $cohaise_api http://api:8080;
proxy_pass $cohaise_api$request_uri;
proxy_http_version 1.1;
proxy_set_header Host $host;
# $remote_addr est l'IP reelle du client (resolue via `real_ip_header`).
# X-Forwarded-Proto doit refleter le schema vu par Cloudflare (https), et non
# $scheme (http, car nginx recoit le tunnel en clair) : sinon le cookie de
# session n'est jamais marque Secure.
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto;
proxy_read_timeout 120s;
proxy_send_timeout 120s;
# La finalisation d'un gros envoi resumable lit et hache le fichier complet
# avant de repondre : 120 s laisse la marge necessaire, sans depasser la
# limite de reponse de Cloudflare (~100 s).
# Aligne sur la borne de depot du Cloud.
client_max_body_size 5g;