Hi Max, I understand your remark. However, in this case "client" also includes all downward caching proxies across the route between DotNetNuke and the end user. In this set up with Apache located directly in front of DotNetNuke as a proxy, the caching is also done at the server side when looking at it from the end user's perspective. The public page is rendered once in every x seconds by dotnetnuke and then stored and served from the cache of Apache for all next visitors in the x seconds. Effectively this reduces the load on the DNN server plus increases response time dramatically (within LAN ever from several hundred milliseconds to 1-2 milliseconds). Ofcourse, it would be better when it can be configured in DNN easily. In this case, Apache was already in place and used as source for the access_logs, so it changes nothing except for an improved end user perception. But I still hope you can build something, since using Apache introduces new complexity for people not yet running it.