[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2034: Ressources not written because restrictive cache almost 100% and cache misses over 70%

[GitBox <gi...@apache.org>]

Lofesa commented on issue #2034:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2034#issuecomment-677509726


   First, you can´t auth any domain that don´t run pagespeed module, so many of the domains you have auth are bad,
   Example, I´m sure wikimedia is not running pagespeed module. What happens when you auth these domain? Pagespeed module rewrites the resource (some like `https://upload.wikimedia.org/some-path/some-file.jpg.ic.pagespeed.SOMEHASH.webp`) but these rewrited resource don´t exists so you get a 404 in return.
   More.  You have `http://.celacp.org/ Auth` but latter you have `https://biblioteca-admin.celacp.org/ Auth`, this make me thinking your own domain is celacp.org and are served by https, but you have http.
   Try to use `http*://*.celacp.org` in this way you have auth both versions http and https, and all subdomains from celacp.org, don´t need separate directives for biblioteca and bilioteca-admin subdomains.
   You have set `SslCertDirectory (assld) /etc/ssl/certs` but don´t have enabled the https fecht `ModPagespeedFetchHttps enable`, You must reviewd the docs about direct fecht https here: https://www.modpagespeed.com/doc/https_support#https_fetch .
   You have set `LoadFromFileCacheTtlMs (lfct) 60000000`, but don use LoadFromFile at all. This directive is an alternate way to load resources from disk other than load it fechting by a http request.
   If you will to use LoadFrom File you must read these doc:  https://www.modpagespeed.com/doc/https_support#load_from_file
   and then enable selective file load https://www.modpagespeed.com/doc/domains#ModPagespeedLoadFromFile.
   
   Any way... the message you have about restrictive cache headers is cause the resources pagespeed will rewrite (and optimize) have a cache-control header not public cacheable. So must have a `cache-control: max-age=some value, public`. Your resources don´t have any cache-control header, and the main request have` Cache-Control: post-check=0, pre-check=0`, I think these header make the request not public cacheable.
   
   When su use debug filter, the debug messages are NOT logged in any log file, nor apache nor pagespeed. The debug messages are in the html code of the page, to read it you need to view the page code


----------------------------------------------------------------
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:
users@infra.apache.org