Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
I ran into a problem live testing ngx_pagespeed 188.8.131.52 beta with nginx 1.4.0.
webpagetest.org reported header
pagespeed online report
nginx.conf settings for gzip
for rewritten js links, should gzip and vary: accept-encoding be removed from the headers ?
@jeffkaufman "I don't think you need to put the charset in gzip_types if that's what you're saying."
I didn't think so either, but this is contradicted when experimentally changing mime.conf
Looses the compression when gzip_types is set to:
When changing gzip_types accordingly to:
The responses for .js files are gzipped again.
I confirm that adding
solved the problem also in my case, with it ".pagespeed." js responses are gzipped, without no.
PS i already had
but this wasn't enough
Another thing which might work well is looking at mime.conf to see what content type we should send out for files served in these manner, as that probably is what gzip_types will target as well. Perhaps that would make configuring this more intuitive.
referenced this issue
May 12, 2013
Updated to Nginx 1.4.2 and 184.108.40.206 beta and seems missing vary: accept encoding bug has returned ? Seem gtmetrix report at http://gtmetrix.com/reports/blog.centminmod.com/kIz3MPiL for Specify a Vary: Accept-Encoding header recommendation missing for both css and js files
wordpress blog has Google SPDY and ngx_pagespeed enabled