oschaaf commented on issue #1870: Proposal: make it possible to cache not rewritten HTML/resources URL: https://github.com/apache/incubator-pagespeed-mod/issues/1870#issuecomment-482518598 My 2p: Maybe it would be worth trying to allow the ipro-flow to record html under certain conditions. I think that in ngx_pagespeed at least, the IPRO lookup flow is completed before initiating the ProxyFetch flow. When recording the html, we would then be forwarding the html both to both the ipro-recorder and ProxyFetch. From thereon it would probably be necessary to make changes to psol to treat html differently from other IPRO content. I can imagine that if we could pull out the cached original html in modules from an IPRO-hit, we could feed it in one go to ProxyFetch again and resume operation as usual. Or maybe we can do that internally in PSOL and just serve the IPRO-hit result. In terms of configuration it would be nice to be able to make this work for common cases that would prevent caching html at the http-level. Maybe masking certain headers/cookies for urls that match configurable patterns would suffice. Otto On Fri, Apr 12, 2019 at 11:50 AM keesspoelstra <notificati...@github.com> wrote: > The biggest problem for a lot of users is a large TTFB caused by long > backend processing, even with relatively static HTML content , with > distributed CDNs there is often no easy possibility to keep all edge nodes > warm. > > As we already see original content when it is generated, we could siphon > it off to a cache item, and use it for subsequent rewrites or even serve it > directly when there are no rewrites. > > Configuration could be done by setting cache control headers to public or > per location via a pagespeed directive. > > Thoughts on implementation and configuration? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-mod/issues/1870>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ACIsRFt-FLhsXcLwmmoII33G0m1lyiA7ks5vgFbcgaJpZM4crwMR> > . >
---------------------------------------------------------------- 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
