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


   Maybe is there some confisuion with ww and non-www
   
![Captura](https://user-images.githubusercontent.com/22342793/85198441-03da8c80-b2e9-11ea-9da6-042c630faf67.jpg)
   
   for that the directive `pagespeed Domain https*://*.webfishki.ru;`
   Note the 2` *` asterisks, one for macht the http(s) and other to macht the 
domain and all the subdomains (*).webfishki.ru
   
   Taking a look at the admin pages:
   In configuration (`https://webfishki.ru/pagespeed_admin/config`), at the 
bottom where the Domain Lawyer, the is https://webfishki.ru but not 
https://www.webfishki.ru so, if you hare changin the doain by some type of 
script or rewrite rule there maybe a problem.
   In the statistis page (`https://webfishki.ru/pagespeed_admin/statistics`) 
you can see the file_cache entries are at 0, so no activity here, this maybe is 
the main problem.
   What do you see taking a look at` /var/cache/nginx/ngx_pagespeed/`? The user 
that runs the nginx process can read/write this directory?
   In the message history page 
(`https://webfishki.ru/pagespeed_admin/message_history`) you can“t see any 
thing, cause pagespeed MessaageBufferSze is set to 0. In this page here comes 
the pagespeed log messages.
   In the cache type page 
(`https://webfishki.ru/pagespeed_admin/graphs#cache_type`) none of the type 
cache are in use. no file cache, none of the databases, no shared memory..... 
despite you have defined a file cache in the config, so there is a big problem.
   When a resource is rewrited ( those that have ***.pagespeed.*** in their 
url) these resource are reclaimed to the pagespeed cache, if no cache is 
working the you get the 404.
   Here you can read about cache and cache type for pagespeed 
`https://pagespeed.apache.org/doc/system`.
   The file cache type need a shared memory cache for the metadada.
   


----------------------------------------------------------------
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


Reply via email to