Lofesa commented on issue #1897: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1897#issuecomment-968957374
Well, this etag header tell me that this request is not managed by pagespeed. Optimized resources have a etag like etag: W/"0" or etag: "PSA/XXXXX" if optimized by the IPRO, an on the fly optimizer that don´t change the url but do some optimizations. I have figured what your site is ( rewied your post) han have discovered some things, relevant to the issue: `https://subdomain.example.com/storeviewgreek/accessories/wilson-greek-flag-dampener-x-1-wr8413601.html?PageSpeedFilters=+debug ` have a `cache-control: max-age=0, no-cache, no-store` this cause problems on the pagespeed cache, this cache don´t store the html code, but need to be public cacheable with max-age GT 0. have a x-magento-cache-control and x-magento-cache-debug headers, this tell me that varnish is in place, because these headers are typically set by varnish config. So you need to take a look at dowstream cache in pagespeed docs [here](https://www.modpagespeed.com/doc/downstream-caching) And now you have these messages in the debug comments `<!--4xx status code, preventing rewriting of` that can be producced by a lot of things, mostly https fechtes fails, but not only. At a 1st step can you disable the varnish config? I think you need to get the web working with pagespeed before introducing varnish in the figure. Maybe there is no varnish but other intermediate cache. -- 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. To unsubscribe, e-mail: dev-unsubscr...@pagespeed.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
