For future reference, it turns out that Rack is calling each twice on the
response_body, see
https://groups.google.com/forum/#!topic/rack-devel/YgEzAlZd8YA
Once i added some checks to only stream once on the second call (rack
closing the connection) it worked as expected! Note: if you only res
Hi Matthew,
I have built a CSV streaming response that suffers from the same problem
that you've described. It seems the larger content amount will delay the
response headers being sent, thus signifying the start of the stream, i.e.
save dialog in browser. It seems this has to do with they web
2 matches
Mail list logo