gzip filter on streaming responses

[John Watson]

That makes much more sense. Thank you for clarifying how the gzip filter
works.

There is a patch forthcoming for the push stream module that adds the
necessary information to get gzip working.

Regards,

John
On Tue, Oct 16, 2012 at 02:41:17PM +0400, Maxim Dounin <mdounin at mdounin.ru> wrote:
> Hello!
> 
> On Mon, Oct 15, 2012 at 02:32:44PM -0700, John Watson wrote:
> 
> > I did some investigation and the gzip filter will only activate if there
> > is a Content-Length header with valid length.
> 
> This is not true.  With Content-Length present gzip filter is able 
> to more effectively allocate buffers (or skip responses as per 
> gzip_min_length), but it isn't limited to responses with 
> Content-Length present.
> 
> > Is there any way of deflating streaming responses from the nginx push
> > stream module? Where is there isn't a  known content length, but
> > potential for thousands of messages to be transferred?
> 
> As long as push stream module does things correctly it should 
> work, but that's the question more about (3rd party) push stream 
> module, not gzip filter.
> 
> 
> -- 
> Maxim Dounin
> http://nginx.com/support.html
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121016/7cb742f7/attachment.bin>