Another question, regarding checking status of upstream. What do you think if change functionality for gunzip to have ability write config like this: if ( $upstream_status = 200 ) { gunzip on; gunzip_options any; } ?by theromis1 - Nginx Mailing List - English
Hi Max, today I've done with your last suggestions. Attaching new patch. Also I've added option "gunzip_strict" when it turned off it adding 32 instead of 16 on inflateInit2 and in case of inflate error in first chunk, sending content unchanged. Please review it and give me recommendations. Default is on. About gunzip_types * by default, in current development version on Nginx I cby theromis1 - Nginx Mailing List - English
ok, I've created patch which must feet nginx rules and my needs, please find it below. when I've checked sources of zlib.h I found this "windowBits can also be greater than 15 for optional zip decoding. Add 32 to windowBits to enable zlib and gzip decoding with automatic header detection, or add 16 to decode only the gzip format (the zlib format will return a Z_DATA_ERROR)." As Iby theromis1 - Nginx Mailing List - English
Perfect Max, understood your style of module, right now I'm working hard to deploy it just with small hacks. Actually we don't need to do unzipping always, we need unzip only for 200 upstream responses and only for text/html answers for reducing load on server. Looks like better to have coordination with your way of development, so I need small instructions how better to do it, and I'll sendby theromis1 - Nginx Mailing List - English
Hi, my company working with ad insertion on Internet traffic. For that I'm trying to use nginx. Some text/html traffic goes with Content-encoding: gzip. So to parse html inside this traffic I've tried gunzip. And it partially works with some hacks. One of my problem was function ngx_http_gzip_ok which returns NGX_OK if in headers doesn't exists Via header, all traffic which I'm passing throwby theromis1 - Nginx Mailing List - English
Hi, I've tried nginx on latest Linux kernel and cant compile it. After little fight with sources I've created patch for that. Just want to ask, is it reasonable? If so, may be better to include it in main branch for Linux build? Please find my patch attached. diff -Naur nginx-0.8.34.orig/auto/os/features nginx-0.8.34.new/auto/os/features --- nginx-0.8.34.orig/auto/os/features 2009-09-30 0by theromis1 - Nginx Mailing List - English