max-age=0 signifies that the response is straight away stale, and must-revalidate implies that it need to not be reused with out revalidation after it is actually stale — so, together, the semantics appear to be similar to no-cache.What must implementations do when cache-Command: no-cache revalidation unsuccessful is just not specified in the RFC