pagespeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-pagespeed-mod] Lofesa edited a comment on issue #1986: Uncacheable content, preventing rewriting of...
Date Tue, 24 Mar 2020 11:33:36 GMT
Lofesa edited a comment on issue #1986: Uncacheable content, preventing rewriting of...
URL: https://github.com/apache/incubator-pagespeed-mod/issues/1986#issuecomment-603186377
 
 
   Hi... This issue is not related to any cache.
   Uncacheable content is related to the http headers cache-control, this header must permit
the asset be cached brownser side.
   Pagespeed need to work these resources referenced in the html code get public cacheable,
some like
   cache-control: max-age=604800,public
   Pagespeed need some hits to work, if you put a cache in front of the web (like varnish),
this cache stores the 1st hit, and serves it witout fechting the background server, so resources
get not optimized. This kind of thing need other config you can see here: https://www.modpagespeed.com/doc/downstream-caching.
   
   When you says you hable enabled caching in the htaccess.conf what do you mean?
   
   EDIT: I´m unable to get debug messages when /PaageSpeed=+debug is used.

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


With regards,
Apache Git Services

Mime
View raw message