: Why don't browsers respect cache headers for initial page request? I'm scratching my head a bit on this. A Drupal site I run is setting appropriate cache headers that should indicate that the

@Dunderdale272

In addition to the other answers, the Expires header is in the past, that is also one reason browsers won't cache the page.

Vote Up Vote Down

@Smith883

You have a Vary: Cookie,Accept-Encoding header in the response. That pretty much means that if the proxy (including your browser) wanted to cache this page it should be prepared to cache a new version for every possibly modified cookie vlaue (or changs in accept-encoding). Especially, it would have to keep a record in the first place of the cookies as they where sent in the request as a distinguishing criterion. I can imagine that either the browser denies this if the cookie is too large (and hence unlikely to be repeate), or it denies it i order to avoid cookie information being leaked via the cache content, or simply the cookie content gets changed on every call.

Vote Up Vote Down

@Murray432

In CMS programs some pages require interaction with the database to display the dynamic content specific to the users request. The entire page can't be cached or it wouldn't show the correct content to the user.

An example of this in practice is an eCommerce shopping cart / checkout page. Since the page looks different every time there's no way to cache it fully. Without knowing more about the specific page it's difficult to know if the page you are referencing requires database involvement.

Vote Up Vote Down