Repository navigation
|
I run AIO behind an external nginx reverse proxy ( What happens When Nextcloud answers a request early, before the client has finished sending a large body, Caddy aborts the response. The client gets the status line and headers, but the chunked body ends without the final The clearest case is a How to reproduce Expected: a complete What I found
A possible fix Adding Workaround for anyone hitting this In the external reverse proxy, answer unauthenticated Environment Debian 13 in an LXC container on Proxmox VE, Podman 5.4.2. The apache image was built 2026-10-29 (Caddy 2.11.7, httpd 2.4.69, Nextcloud 34.0.5.1, PHP 8.4). I searched existing issues and Discussions and didn't find this problem reported. Disclosure: an AI assistant (Claude) helped me diagnose this problem and draft this report. I reviewed the text and ran the reproduction steps above myself. |
Replies: 1 comment
|
Hello, I can't confirm this on beta, my guess is that this was fixed in golang/go@bdd49b5 which beta includes, but latest not |
Hello, I can't confirm this on beta, my guess is that this was fixed in golang/go@bdd49b5 which beta includes, but latest not