On 17 May 2010 11:50, Ben Timby <[email protected]> wrote: > On Wed, May 12, 2010 at 7:43 PM, Graham Dumpleton > <[email protected]> wrote: >> Can you actually reliably reproduce this issue? > > I can reliably reproduce this issue. It always fails at the same byte, > causing me to think there is a limit somewhere. Like I said, this > setup worked fine with mod_python, and I only started having issues > when I moved to mod_wsgi. > > I have already updated the production servers to use X-Accel-Redirect. > As you said, this is a much better solution all around.
I asked you: """ Are you using wsgi.file_wrapper to optimise serving the file, or using your own mechanism for streaming. """ Can you at least answer that question so I might now where to start looking? An actual piece of code showing how you are streaming file back would be ideal. I know that when streaming yourself, that there are issues if you were silly enough to return a single 2GB or greater string, presuming you have enough memory, but if you use wsgi.file_wrapper, don't know of any issues. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
