Note that any changes you make to the httpd.conf file will be effective upon starting or re-starting Apache HTTP Server.

Step 1: Enable mod_cache and mod_cache_disk in Apache HTTP Server

Load mod_cache and mod_cache_disk dynamically, using the LoadModule directive; that means un-commenting the following lines in the httpd.conf file:

LoadModule cache_module libexec/apache2/mod_cache.so
LoadModule cache_disk_module libexec/apache2/mod_cache_disk.so

Step 2: Configure Apache HTTP Server's caching features

Include the following Cache directives in the context (protocol type, virtual server, or location) for which you want to cache server responses:

<VirtualHost *:80>
	...
	
	CacheRoot  /etc/apache2/cache/
	CacheEnable disk /
	CacheDirLevels 2
	CacheDirLength 1
	CacheHeader on

</VirtualHost>

• The CacheRoot directive defines the name of the directory on the disk to contain cache files. You must ensure that the user running the Apache service has read/write access to this directory.
• The CacheEnable directive instructs mod_cache to cache urls at or below url-string and cache_typedisk to instruct mod_cache to use the disk based storage manager implemented by mod_cache_disk.
• The CacheDirLevels directive sets the number of subdirectory levels in the cache. Cached data will be saved this many directory levels below the CacheRoot directory.
• The CacheDirLength directive sets the number of characters for each subdirectory name in the cache hierarchy. It can be used in conjunction with CacheDirLevels to determine the approximate structure of your cache hierarchy.

• When the CacheHeader directive is switched on, an X-Cache header will be added to the response with the cache status of this response.

Step 1: Include proxy_cache_path to the top‑level http context

Include the proxy_cache_path directive in the top‑level http context; that means add the following line to the nginx.conf file:

http {
    ...
	proxy_cache_path /data/nginx/cache levels=1 keys_zone=bamboo_server:10m max_size=1024m inactive=20m use_temp_path=off;
}

The mandatory first parameter is the local filesystem path for cached content, and the mandatory keys_zone parameter defines the name and size of the shared memory zone that is used to store metadata about cached items.

• You must ensure that the user running the NGINX service has read/write access to this directory.
• In this example we'll name the cache bamboo_server and limit the amount of cached response data to 1024m.
• Set inactive to 20 minutes. Cached data that are not accessed for over 20 minutes get removed from the cache regardless of their freshness.

Step 2: Include add_header and proxy_cache to start caching responses

Include the add_header directive using the 'X-Cache-Status' name and value '$upstream_cache_status'. This way the X-Cache-Status header will be added to the response with the cache status of the response. Include the proxy_cache directive in the context (protocol type, virtual server, or location) for which you want to cache server responses, specifying the zone name defined by the keys_zone parameter to the proxy_cache_path directive (in this case, bamboo_server):

server {
	...
	add_header           'X-Cache-Status' '$upstream_cache_status';
	location / {
    	...
    	proxy_cache           bamboo_server;
  	}
}

There are several other attributes you can add to tweak cache settings, as pointed out in the NGINX Content Caching documentation. This is highly customizable. However, as mentioned previously in this article, for remote agent content caching you just need to enable the content caching on the proxy and Bamboo will tell the cache what to store.