Lofesa commented on issue #1148: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1148#issuecomment-829950357
Hi Sound strange. PageSpeed has nothing to do with the brotli module or even gzip. Only if `HttpCacheCompressionLevel` is enabled it stores the optimized resource gziped and serve it compressed, if set to 0 the optimized resource is stored w/o compressing it and served as it is, then nginx compression modules compress the optimized resource. Yes, header manipulation is an old question related on how nginx work (the order nginx processes modules).See. https://github.com/apache/incubator-pagespeed-ngx/pull/906 and https://github.com/apache/incubator-pagespeed-ngx/issues/1005#issuecomment-160901857 and you can use `pagespeed AddResourceHeader "X-Foo" "Ba\nr";` too If you only enables image filters.... well there is a PageSpeed function that work when PageSpeed don´t fully optimize resources: IPRO (https://www.modpagespeed.com/doc/system#ipro), an on the fly optimization, and there is an other side that maybe considered, the rewrite level, by default (if you don´t set any other rewrite level) is corefilters, this enables a set of filters. See: https://www.modpagespeed.com/doc/config_filters.html#level. If you only need these filters you will and none of the others filters you need to set: `pagespeed RewriteLevel PassThrough;` This only enable the filters you have explicitly set. And maybe you need some like: `pagespeed ForbidAllDisabledFilters true;` to not permit the use of filters not explicitly enabled. -- 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
