I browse my development site using the Yslow tool in Chrome and Firefox, and one of the suggestions is that I gzip the relevant content. As a starting point, I simply added "tools.gzip.on = True" to my [/] configuration. I know that the configuration file and the block are processed correctly, because I also added options for disabling caching in the response headers, since I often change files when developing a site. In my answers, I see the headers "Expires" and "Pragma: no-cache".
For some reason, even after changing the configuration file (and restarting the process, which is not absolutely necessary), Yslow still reports that I am not using gzip. I also used wget and don't see the Content-Encoding header.
Can anyone suggest how else can I check what is happening? I am wondering if the cherry problem is ignoring the gzip setting, or if Yslow is simply mistaken in its facts. I have never had a problem with Yslow before, so I lean toward the first.
I will add that Yslow only says that my external CSS and JavaScript files (served by the same swirl process) should be compressed, although the headers shown by "wget -S" do not show gzip encoding even on the main page (which is dynamic content).
I tried to add "tools.gzip.on = True" to my [/ css] and [/ js] blocks, and I also tried to set the "tools.encode.on = True" parameter in all the same blocks, assuming the encoding must be enabled for gzip to work.
Thanks in advance.
source
share