Geek asks and answers

"no-cache" vs "max-age = 0, must-revalidate, proxy-revalidate"

What is the difference between HTTP response with Cache-Control: no-cachevs Cache-Control: max-age=0, must-revalidate, proxy-revalidate?

Do browsers have the same thing?

+5
source share
1 answer

In general, different browsers do not behave exactly the same. HTTP cache headers.

The small difference that I remember (I can’t find the source, so I’m not 100% accurate description of the behavior) is that Chrome (afair) processes max-age=0it as if you had specified max-age=10(provided that the difference in behavior is small enough, but performance impact still makes sense).

Anyway, here are some other examples of differences in the behavior of the HTTP cache between browsers:

  • HTTP 1.0 Cache (Pragma), HTTP 1.1.
  • (FF +?) no-store
  • no-cache, public, - .
  • IE max-age, vary.
  • .

Cache-Control: no-cache, must-revalidate, proxy-revalidate, pragma: no-cache (HTTP 1.0), Expires: 0, , .

+2

More articles:


All Articles