Discuss: Cache Control Directives Demystified
by Siddharth Anbalahan
You wrote :
--------
Cache Control: must-revalidate
This directive insists that the browser must revalidate the page against the server before serving it from cache. Note that it implicitly lets the browser cache the page. The “no-store” directive is a safer option if you want to prevent a sensitive page from being stored on the browser.
--------
I believe that is not true :
Check the rfc2616
The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances an HTTP/1.1 cache MUST obey the
must-revalidate directive; in particular, if the cache cannot reach the origin server for any reason, it MUST generate a 504 (Gateway Timeout) response.
This is probably the most clear and concise explanation of cache control headers i've run across yet... nice job.