Joshua Marantz

Yes, best practice is to use a local shared-memory on each server, with a shared redis/memcached backend. In that scenario, the local shared-memory cache will store metadata, which tells pagespeed...

No, if you have two totally unrelated html pages both of which reference the same exact image for the same Accept request-header, and the same width/height context, the metadata cache...

From a functionality perspective, it is fine to have PageSpeed running on multiple servers with isolated caches. You will wind up storing each resource and re-optimizing each image on every...

What is the MPS version in question? The PURGE method is not on by default yet in 1.9 (latest beta & stable), so it should work to touch the cache.flush...

I don't think underlying protocol matters that much to PageSpeed, other than a few http2-related optimizations that have been attempted in the past. Could you say more about what's going...

No known issues, but it wouldn't surprise me to learn there were incompatibilities between the nginx plugins for pagespeed and quic. I don't have any further details though. I think...

PageSpeed, AFAIK, would not touch such a header. It leaves alone all headers it doesn't have specific handling for.

What do you need to add that `#include` into? pagespeed_automatic.a is an intermediate library which can be used to build the Apache or nginx versions.

PageSpeed doesn't optimize video itself. I'm not certain but you might be able to get it to proxy and cache-extend a video file using https://www.modpagespeed.com/doc/domains#url-valued-attributes . However, I'm not sure...

You are right that no one is actively working on the feature, but if there's some usage issues you might want to refer to the test code which can clarify...