Expires: vs. Cache-Control: max-age

[Chris Woodfield <rekoil@xxxxxxxxxxxxx>]

Hi,

Can someone confirm whether Expires: or Cache-control: max-age  
parameters take precedence when both are present in an object's  
headers? My assumption would be Cache-control: max-age would be  
preferred, but we're seeing some behavior that suggests otherwise.

Specifically, we're seeing Expires: headers in the past resulting in  
refresh checks against our origin even when a Cache-Control: max-age  
header is present and the cached object should be fresh per that metric.

What we're seeing is somewhat similar to bug 2430, but I want to make  
sure what we're seeing isn't expected behavior.

Thanks,

-Chris