Joshua Marantz

I suspect deleting that line would cause all kinds of tests to need to be regolded. It would also be worse generally for performance because it makes the HTML bigger...

Re-opening as this fix depends on a kernel not everyone has.

Cache eviction should not cause a 404 unless something else is wrong. Cache expirations also happen. Is it possible that the origin asset moved?

That does not look like the result of MapProxyDomain. Can you share your other domain-related config?

RE "long time to load": that should not cause 404; it should cause PageSpeed to elect not to optimize that resource. RE "`pagespeed Domain https://fonts.googleapis.com;`" that is definitely wrong. You...

Do you have downstream caching enabled? E.g. a Varnish cache between pagespeed and your clients? If so, can you flush that cache and see if the problem persists? Maybe there...

Sorry about my confusion -- I think your config looks OK mostly, and there's a possibility of a bug, because the example page for MapProxyDomain is broken also. The only...

one other thought: maybe ngx_pagespeed is not activated on `https://$host/source_img/` and you should map your externally hosted assets onto ` https://$host/some_directory_with_pagespeed_enabled/source_img`?

josh: Can you work around this short term with: ModPagespeedDisallow *megahuge.css aroman: Yes, disabling optimization for the affected css files works. josh: You know your way around our code. You...

The original resource may be in the cache (it's not necessarily a file-cache in general; could be memcached or redis) but it may be evicted or expired. In any case...