jmarantz commented on issue #1685: Pagespeed causes high FTTB on nginx URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1685#issuecomment-613192821 Yeah it's probably easiest if you stick with the optimization that don't require modifying URLs in HTML. I'd use OptimizeForBandwidth <https://modpagespeed.com/doc/optimize-for-bandwidth>. You won't get combine_css but you'll get compression and minification. What I don't remember is whether setting that mode also allows retention of the origin html caching headers. But if it doesn't you can use https://www.modpagespeed.com/doc/configuration#ModifyCachingHeaders pagespeed ModifyCachingHeaders off; On Mon, Apr 13, 2020 at 9:48 PM Jake Edwards <notificati...@github.com> wrote: > Yes, seems to be the default cache taking control here: > > *If no Cache-Control is present the default behavior is that AFD will > cache the resource for X amount of time where X is randomly picked between > 1 to 3 days.* (source > <https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching#cache-expiration> > ) > > Is it possible to get PageSpeed to just serve cacheable assets as > Downstream Cache config won't work with Azure Front Door. I would like to > just use the Javascript, CSS Concat and Compression, or are they dependant > on the beacons? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-ngx/issues/1685#issuecomment-613181611>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAO2IPKA5TOCFCTM6CHTGQTRMO6H3ANCNFSM4MDTLW7Q> > . >
---------------------------------------------------------------- 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
