[GitHub] [incubator-pagespeed-mod] jmarantz commented on issue #1148: Support Brotli as an encoding scheme when client has Accept-Encoding

jmarantz commented on issue #1148: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1148#issuecomment-830673351 I think that makes sense. PageSpeed doesn't know anything about Brotli right now so if caches gzipped content and sends it to clients, the Brotli module may not

[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #1148: Support Brotli as an encoding scheme when client has Accept-Encoding

Lofesa commented on issue #1148: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1148#issuecomment-830665677 Hi @jmarantz When `HttpCacheCompressionLevel` has a non zero as value, the optimized resources are served gziped, no matter if you have brotli module in place. I

[GitHub] [incubator-pagespeed-mod] jmarantz commented on issue #1148: Support Brotli as an encoding scheme when client has Accept-Encoding

jmarantz commented on issue #1148: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1148#issuecomment-830645514 I don't think you should need to flush the pagespeed cache when changing options. A hash of all the options are incorporated into the cache keys. However I

[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #1148: Support Brotli as an encoding scheme when client has Accept-Encoding

Lofesa commented on issue #1148: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1148#issuecomment-830592421 Yes, maybe a cache issue. If you change `HttpCacheCompressionLevel` to 0 and don´t clean the pagespeed cache, by default this level is set to 9 (if I remember), so