i am sending large (400mb) csv files using nginx, using https.
sometimes not the whole file is served by nginx.
it simply closes the connection before the whole file is sent.
if the downloader supports resuming, then the file-download can be
the file is served using the “X-Accel-Redirect” technique (it’s
authenticated on a proxied apache server, and then the file is served
directly by nginx)
when such problems happen, the error-log contains this:
2007/12/17 01:02:03 [crit] 21821#0: *864836 SSL_write() failed (SSL:
error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry) while
sending response to client, client: 22.214.171.124, server: www.example.com,
URL: “/some/url/to/a.csv”, upstream:
“http://internal-ip/some/auth/url/a.csv”, host: “www.example.com”
debian lenny (it has nginx 0.5.30-1)
any ideas why is this happening?
also, i checked the release-notes for 0.5.34, and it says:
Bugfix: the big responses may be transferred truncated if SSL and
gzip were used.
can this be somehow related to it?
is there a bug-database for nginx? so is there a way to check what this