Lofesa commented on issue #1681: Uncacheable content, preventing rewriting of image URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1681#issuecomment-593925907 Well... Where the plesk panel put these directives? in a vhost config file? If yes, you don´t need to set the pagespeed directives in the htacces again. If I remember, the config files in apache have sections, like VirtualHost, Directory, Location or Files. I don´t know how Plesk work, but I bet that it creates a file with 2 VirtualHost for http an https, and the default directives for Directory and so.... The pagespeed directives you put here are for the whole site, you no need to duplicate it in any htacces. Htacces are files to overwrite config setings in a directory (you can have a htacces file in each directory). Unless you need to enable (or disable) a diferent set of filters in that directory. 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. 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. Are you hitting the apache web server directly or you have configured cloudflare to bypass for your ip? I can´t see the changes you made in config, so I still getting the infinite loop. 
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
