Stop the 60s entrypoint read timeout capping uploads

FixKlusterServices
Ya
8 Agosti 2026, 02:36 UTC
Mwandishi
Kamo
Ahadi ya
106097b

respondingTimeouts.readTimeout is the deadline for reading a WHOLE request, body included, and Traefik v3 defaults it to 60s where v2 had no limit. That silently capped every upload in the platform at whatever fits in a minute. Chat attachments now go to 3 GiB, which at the default would need a ~400 Mbps uplink to arrive at all; anything slower was cut off mid-transfer with nothing the app could explain. One hour is generous for 3 GiB and still bounds a connection that stops sending. Header-only slowloris stays covered by the backends' own header deadlines.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei