<div>Have you tried?</div><div><br></div><div>           gzip on;</div><div>           gzip_min_length 0;</div><div><br></div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px">Reg</span>ards,</div><div><br></div><a href="http://www.twitter.com/jdorfman" target="_blank">Justin Dorfman</a><br><br>
<a href="http://www.netdna.com" target="_blank">NetDNA</a>™<br>The Science of Acceleration™<br></span><div></div><br>
<br><br><div class="gmail_quote">On Mon, Oct 15, 2012 at 2:32 PM, John Watson <span dir="ltr"><<a href="mailto:john@disqus.com" target="_blank">john@disqus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I did some investigation and the gzip filter will only activate if there<br>
is a Content-Length header with valid length.<br>
<br>
Is there any way of deflating streaming responses from the nginx push<br>
stream module? Where is there isn't a  known content length, but<br>
potential for thousands of messages to be transferred?<br>
<br>
Regards,<br>
<br>
John<br>
<br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br></blockquote></div><br>