> Since I posted the message below I've done a bit more investigation > and discovered that the response returned when running under uWSGI > uses chunked transfer encoding, whereas when I switch back to using > apache/mod_wsgi it doesn't use chunked transfer encoding. I haven't > changed the nginx configuration except to swap from an apache backend > to uwsgi. The app code hasn't been changed in any way either. > > Anyway, here's the response header when I use Nginx/Apache/mod_wsgi: > > Connection close > Content-Encoding gzip > Content-Length 135 > Content-Type text/html; charset=utf-8 > Date Wed, 25 Jan 2012 23:15:16 GMT > Server nginx > Vary Cookie,Accept-Encoding > > Here's the response header when I use Nginx/uWSGI: > > Connection close > Content-Type text/html; charset=utf-8 > Date Wed, 25 Jan 2012 23:18:12 GMT > Server nginx > Transfer-Encoding chunked > Vary Cookie > > >
It looks like you have enabled gzip in apache config, that's why nginx manages them differently. By the way can you post nginx config for both mod_wsgi and uWSGI and uWSGI config ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
