cache-control max-age

[pmeenan]

Yes, in a forced refresh it is normal for the client to request max-age: 0

That is the browser's way of telling the server and any intermediate proxies that it needs the current version of the file and not to serve a version that was cached somewhere along the path. A reload of the page behaves very differently from actually navigating to a page for a second time. WebPagetest's repeat views are done by closing the browser and then loading the page again in a new instance (browsers have an in-memory cache that behaves differently from the normal caching as well which is why we close the browser out).

Thanks,

-Pat