oschaaf commented on issue #1692:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1692#issuecomment-640866476
For `gzip_static`, I think it matters if the origin involved is low latency
and high bandwidth or far off. Concretely, if a hypothetical ngx_pagespeed
enabled proxy runs in front of a far-away origin with limited bandwidth and
high latency, then gzipping static content could make sense. On the other hand,
if both reside in the same datacenter -- or even process, then the extra cycles
spent on compressing/decompressing might not make a lot of sense sense.
So given the above, instead of a generic recommendation, I'd be more in
favor of describing such scenarios in our docs.
It's also worth mentioning that regardless of nginx's configuration,
pagespeed modules cache compressed versions for serving for resources where
that makes sense.So I think `gzip_static` primarily applies to what happens
when pagespeed fetches it's input resources. That leaves the case for serving
static html. ngx_pagespeed will enable dynamic gzip compression when gzip isn't
configured in nginx, as the static html by definition no longer is static when
it flows through a pagespeed module.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
