mod_memcached

mod_memcached caches content on memcached servers

lookup tries to find data associated with the key, and returns it as http body with status 200 if it finds something.
store stores a http body (generated by another backend) in memcached.

Caching always requires you to think about what you want; you cannot cache content that changes with every request!

So most of the time you probably want to set a TTL for the stored content in memcached; your users probably don’t need new content to be available the next second, perhaps 60 seconds is still good (obviously not true for a chat…).

The other way is to purge the keys in your dynamic backend; you can set the memcached content from your backend too, which probably is faster than memcached.store.

If the key is longer than 255 bytes or contains characters outside the range 0×21 – 0×7e we will use a hash of it instead (for now sha1, but that may change).

memcached.lookup (options, action-hit, action-miss);

memcached.store options;

setup {
	module_load "mod_memcached";
}

memcached.lookup (["key" => "%{req.scheme}://%{req.host}%{req.path}"], {
	header.add "X-Memcached" => "Hit";
}, {
	header.add "X-Memcached" => "Miss";
	docroot "/var/www";
#	important: You need a content handler before memcached.store
	static;
	memcached.store ["key" => "%{req.scheme}://%{req.host}%{req.path}"];
});