Skip to content

security(deploy): nginx client_max_body_size 100M → 120M #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mpasternak merged 1 commit into from
Jul 12, 2026
Merged

security(deploy): nginx client_max_body_size 100M → 120M #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion defaults/webserver/vhost.conf.template
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,19 @@ server {

# Main HTTPS server block for ${VHOST_NAME}
server {
client_max_body_size 100M;
# Twardy cap na rozmiar pojedynczego requestu = ostatnia bariera na krawedzi
# przed uploadem (defense-in-depth obok limitow app-layer z bpp#551:
# 5 plikow x 20 MiB + DATA_UPLOAD_MAX_NUMBER_FILES). UWAGA: legalny maks
# zgloszenia to 5 x 20 MiB = 104857600 B = DOKLADNIE 100 MiB samych plikow,
# a request niesie jeszcze narzut multipart (granice, naglowki per-part,
# pola formsetu autorow, CSRF) - przy dawnym `100M` (== 100 MiB) najwieksze
# POPRAWNE zgloszenie dostawalo 413 zanim dotarlo do Django. 120M daje ~20
# MiB zapasu na narzut, nie oslabiajac istotnie bariery (i tak > od limitow
# app-layer, a rate-limit per-IP ogranicza czestotliwosc). Podniesienie capu
# nie psuje wiekszych uploadow innych endpointow (importy w /admin/) - moze
# je tylko przepuscic. Bind-mount wersjonowany -> `git pull && make up`
# aktywuje bez migracji.
client_max_body_size 120M;

listen 443 ssl;
listen 443 quic;
Expand Down
Loading