ws420 edited a comment on issue #1681: Uncacheable content, preventing 
rewriting of image
URL: 
https://github.com/apache/incubator-pagespeed-ngx/issues/1681#issuecomment-594181431
 
 
   > This:
   > # Header set Cache-Control "no-store, no-cache, must-revalidate, max-age=0"
   > makes all resources uncacheable, so pagespeed can´t optimize it. You need 
to enable it, but with some like:
   > Header set Cache-Control "max-age=86400, public"
   > This make resources cacheable for 1 day, so pagespeed can optimize it and 
when optimized, it changes to 1 year.
   
   We have a lot of dynamic content on the website that needs to be updated 
every 5 minutes or so (news and live market data). Does this means that 
everything will be cached for 1 day on the website? We are looking to cache 
only the images, css, js
   
   > I think nginx still working, as far I can see the header x-pagespeed that 
is set by nginx.
   > If the working module of pagespeed is in apache server these header must 
be X-Mod-Pagespeed.
   
   I'm confused. I have no idea what's going on. If I disable nginx in Plesk it 
doesn't work.
   
![image](https://user-images.githubusercontent.com/48076840/75821430-409b6b80-5d6c-11ea-909f-058544686cb6.png)
   You would think the settings above would completely disable nginx but 
instead is seems that it disables apache and runs only on nginx! As soon as I 
disable the proxy mode, the htaccess stops working and the url rewriting 
returns 404 errors on all wordpress pages
   
   I also tried via the CLI:
   `plesk bin domain -u weedstreet420.com -nginx-serve-php false`
   
   > 
   > Ah! your site is https, so you need to configure fechthttps or 
loadfromfile.
   > By default, pagespeed tries to fecht resources by http, and maybe the 404 
error´s you see is for don´t have the https enabled.
   > 
   > ModPagespeedFetchHttps enable
   
   We tried enabling FetchHttps but the entire website will return an Internal 
Server Error as soon as it's 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


With regards,
Apache Git Services

Reply via email to