'Connection reset by peer' when replying before the end of POST data

Lunar lunar at anargeek.net
Fri Mar 2 16:29:42 UTC 2012

Lunar wrote:
> Using this, I get the following results:
>   - curl: 413 displayed, 1.4K
>   - w3m: 413 displayed, 8.8M
>   - iceweasel: 413 displayed, 8.8M
>   - epiphany: 413 displayed, 8.8M
> This whole issue leaves me severely disappointed. It looks like I either
> have to waste much of my users time (by forcing them to upload the whole
> file) or leave them clueless if the file is too big (by cutting the
> connection early, resulting in a "reset by peer message"). What a
> choice…

Just for the record, reverse proxying this last iteration with Nginx
(with "proxy_buffering off;") or Apache (with
"SetEnv proxy-sendchunks 1") result in 413 displayed and full
transmission of the given file with all clients (curl included).


More information about the rainbows-talk mailing list