NGINX compile and gzip config (with rails 3 + php-fpm): "can't unzip" by torrent client from php tracker -
hi there: have got weird question new server installed nginx+php-fpm+passenger. latest version. have got configured well, web pages running, when users tried access php tracker of private tracker, returns them error: "can't unzip". utorrent. on vuze java gzip exception saying it's not valid gzip file or so, shows server has been returning gzip data clients don't understand.
so here's nginx.conf:
user www-data; worker_processes 4; events { worker_connections 1024; } http { passenger_root /home/meng/.rvm/gems/ruby-1.9.2-p136/gems/passenger-3.0.2; passenger_ruby /home/meng/.rvm/wrappers/ruby-1.9.2-p136/ruby; include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; gzip on; gzip_static on; gzip_disable "msie [1-6]\.(?!.*sv1)"; gzip_comp_level 2; gzip_vary on; gzip_proxied any; gzip_types text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript; include /opt/nginx/conf/sites-enabled/*; }
the nginx compiled passenger arguments of: --with-http_stub_status_module --with-http_gzip_static_module based on tutorial stated here http://geeksharp.com/2010/09/14/nginx-rails-and-php-round-2/ guess gzip problem, have solutions server return correct gzip data, clients eat it? much.
try turning off gzip_static dynamically generated locations. gzip_static try create .gz file in same directory request, , may cause issues php, ruby, etc.
also, i'd turn gzip_comp_level 5 or 6, if caching compressed file gzip_static.
Comments
Post a Comment