gzip compression not taken into account?

[Jocelyn]

Hi,

Maybe you'are encountering what Steve Souders call the "Turtle Tapping".

You need to check the Accept-Encoding HTTP header from the browser side
(need to be: Accept-Encoding: gzip, deflate). In some cases (in order to
analyse faster the content of the traffic), web-proxies and Antivirus are
mangled the Accept-Encoding HTTP header.

--
Regards
       Jocelyn Mocquant


On Fri, May 13, 2011 at 1:19 PM, Dan Trainor <dan.trainor at gmail.com> wrote:

> Hi -
>
> Are those tools misreporting?  What does the content-encoding: header say?
> On May 13, 2011 1:09 PM, "jfix" <nginx-forum at nginx.us> wrote:
> > Hi, I have enabled gzip compression following the wiki instructions like
> > this:
> >
> > location / {
> > #....
> >
> > gzip on;
> > gzip_min_length 1000;
> > gzip_proxied expired no-cache no-store private auth;
> > gzip_types text/plain application/xml text/javascript text/css
> > application/x-javascript;
> > gzip_disable "MSIE [1-6]\.";
> >
> > #...
> > }
> >
> > unfortunately, both Yahoo's yslow and Google's pagespeed tell me that I
> > should enable compression for better performance.
> >
> > How can I find out why compression doesn't seem to happen? I've
> > selected the mime-types after having looked at them in chrome's web
> > inspector.
> >
> > Thank you in advance,
> > Jakob.
> >
> > Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,197898,197898#msg-197898
> >
> >
> > _______________________________________________
> > nginx mailing list
> > nginx at nginx.org
> > http://nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110513/c324747d/attachment-0001.html>