100% Resources not rewritten because of restrictive Cache-Control header

[Christopher Felpel]

Having a lot of problems solving this issue. I have two sites on the same server with the same IIS, Pagespeed settings and cache-control headers but the one is showing 100% failures for rewrites due to cache control headers. Any ideas on what else I should look at or convey back to this thread will be greatly appreciated.

Trouble Shooting Steps

1. Verified Cache-Control headers for various types of resources are set to no-cache which I believe is the desired response.

2. Compared IIS Configs between the sites that work and don't.

3. Verified Codebase versions are identical.

4. Verified Pagespeed configs are identical.

Anything else I can check or report back?

[Otto van der Schaaf]

+Support (accidentally dropped it from my reply)

On Sat, Jul 9, 2022 at 11:24 AM Otto van der Schaaf <osc...@we-amp.com> wrote:

Hi Christopher,

"no-cache" is not the desired response; the module will only rewrite resources that are cacheable -- and then

check back at the specified max-age to see if optimizations need to be re-computed. So it tried to respect the

http cache/expiry directives.

When possible, instead of tweaking http response headers, we usually recommend setting up loadfromfile:

https://www.pagespeedguide.com/documentation/url-routing/load-from-file

Doing that comes with other perks too, improved input loading speed and instant updates to the optimized

versions when a resource changes (but obviously this is only possible for resources that actually reside on disk).

Hope that helps!

Kind regards,

Otto van der Schaaf

https://www.linkedin.com/in/oschaaf

We-Amp B.V.

Aalsmeerderweg 14

1432 CR Aalsmeer

The Netherlands

E-mail: osc...@we-amp.com
Website: www.we-amp.com