Lofesa commented on issue #1742: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1742#issuecomment-954935119
Hi HttpCacheCompressionLevel stores optimized resources gziped in pagespeed cache and serve it as gzip with content-encoding: gzip header. If you set HttpCacheCompressionLevel to 0 (gzip disabled) then the resource is stored w/o "gziping" it and served w/o content-encoding header, then the web server need to compress it (whatever compression is enabled) and set the content-encoding header. For example, HttpCacheCompressionLevel must be set to 0 if you will resources be compressed by brotli. For the img.domain.com issue my bet is pagespeed is requesting resources via http and store it in the http cache, client is requesting the resource via https and there is no https version in the pagespeed cache. Is `http://www.domain.com` accesible? If yes, can you try it an see whats happens with rewrited resources ( 404 or 200) So the question is why pagespeed is fechting http resources and not https? Where are the config directives, server block, location block.. ? ``` pagespeed FetchHttps enable; pagespeed SslCertDirectory /etc/ssl/certs; ``` must be set at host or servers blocks not in location ones. What certificate is in use at img.domain.com, Is a selsigned certificate? is a valid one? -- 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. To unsubscribe, e-mail: dev-unsubscr...@pagespeed.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
