3 ms·

If you go back and read the RFC for http, don't we have the headers to do this already, and the browsers just don't behave that way? http://www.w3.org/Protocols

If you go back and read the RFC for http, don't we have the headers to do this already, and the browsers just don't behave that way? http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14... If that is true wouldn't a "strict" cache control make a whole lot more sense?

manigandham 11y ago
Yes, technically browsers should just skip the revalidation if the header already has a max-age, since that's what the caching time is. And yes, having more uniform and standardized approach to caching would be better.