Ok, I'm done with regards to this investigation. In case someone is curious, it seems the problem only happen with unicorn set to preload the application and with the following Rails config options enabled:
config.cache_classes = true config.eager_load = true Any of those options enabled was enough for the streaming to fail. Unicorn was configured with tcp_nopush: false by the way, in case you were curious. I still don't know exactly why the application wasn't working with streaming (we set the http version to 1.1 in nginx) but I won't continue this investigation because even if we could get unicorn to work with streaming it wouldn't be a good thing to do in our case, since our streaming actions can be really slow and we don't want to take the risk of the "export to excel" feature to use all available Unicorn workers, so we'll redirect those actions to another multi-thread server or we'll deploy the full application with Puma, maybe. But maybe this could help others that might face the same problem concerning live streaming and unicorn/nginx. Regards, Rodrigo. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
