The receiving end is just a browser but I've noticed a higher failure rate with chrome/windows vs chrome/Linux and osx.
I'm using with files in the 5 to 11GB size ranges On Thu, 12 Mar 2015 19:04 Tim Tisdall <[email protected]> wrote: > On Thu, Mar 12, 2015 at 3:01 PM, Tim Tisdall <[email protected]> wrote: > > On Thu, Mar 12, 2015 at 2:32 PM, John Goodyear <[email protected]> > wrote: > >> Hi > >> I tried values upto one hour but downloads which took < 5 minds could > still > >> generate the timeout issue. > >> > >> It didn't feel right that I have to guess the maximum time it may take > to > >> download a file. > > > > Are you writing to the file and then trying to send it? Maybe you're > > calling sendfile before it's finishing writing everything to the file > > and sendfile is timing out on acquiring the file lock? The fact that > > it's an intermittent issue hints at some sort of race condition. > > Hmm.. I see that you're getting a "write error" though... Is it > possible the receiving end has a timer and is cancelling the transfer > before it's finished? > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
