Caching in concrete5 affects database queries, not what is actually being sent to the browser.

For example, with caching on, a "page list" block won't query the database every time the page is loaded.

thanks for the reply.

I wanted to use varnish as reverse proxy for apache. Varnish uses few of the http response headers (Cache-Control, Age,Date, Etag) from apache. But concrete5 does not return any of these headers correctly.
I tried modifying these headers in apache config file but this has been ignored and concrete5 pages always returns no-cache (Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0).

Is there any way getting these headers correct?

Thanks

Hey, Did you ever find a solution to this? We're trying to use Varnish but it's useless with these headers being returned.

The cache has been completely re-designed since this thread. Have a look through the 5.6+ series of release notes. I think there may also be a howto on Varnish.

There's also this:
https://github.com/concrete5/addon_varnish_cache...