From 5b5a12e57c086971cd02042f98f68153279cd77b Mon Sep 17 00:00:00 2001 From: sneak Date: Thu, 19 Nov 2026 08:51:32 +0000 Subject: [PATCH] README: raise traefik's read timeout with rproxy's for large git pushes The commented rproxy lines said a git push may take up to 10 minutes to send, but traefik v3 gives a whole request, body included, 60 seconds by default, and answers 502 to a slower one. A commented traefik line now raises its readTimeout to match. Model: opus-5-5 --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 68ebfe5..8e25d77 100644 --- a/README.md +++ b/README.md @@ -476,6 +476,9 @@ services: - --certificatesResolvers.le.acme.email=hostmaster@example.com - --certificatesResolvers.le.acme.storage=/letsencrypt/acme.json - --certificatesResolvers.le.acme.tlsChallenge=true + # Give a request 10 minutes to arrive, rather than 1, for the + # large git pushes the rproxy lines below accept. + # - --entryPoints.websecure.transport.respondingTimeouts.readTimeout=600s ports: - "80:80" - "443:443" @@ -495,7 +498,8 @@ services: SWW_RPROXY_WAF_BACKEND: http://waf:8080 SWW_RPROXY_UPSTREAM_URL: http://app:3000 # Accept git pushes up to 1 GiB, rather than 100 MiB, sent in - # up to 10 minutes, rather than 1. + # up to 10 minutes, rather than 1, with traefik's readTimeout + # line above. # SWW_RPROXY_MAX_REQUEST_SIZE: 1G # SWW_RPROXY_MAX_REQUEST_TIME_MS: "600000" labels: