trafficserver

To avoid unnecessary cache writes, there's also a plugin that does implement a rudimentary LRU. Basically, you have to see some amount of traffic before being allowed to get written to the cache. This is typically done in a scenario where it's ok to hit the parent caches, or origins, once or a few times extra. It can also be a very useful way to avoid too heavy disk write load on SSD drives (which can be sensitive to excessive write wear, of course). See https://github.com/apache/trafficserver/tree/master/plugins/...

Apache Traffic Server has support for native C++ plugins which allow you to make transformations to the headers and the body as the request and response passes through it. ATS's power comes mainly from these plugins, I would say, rather than just a reverse caching proxy. https://github.com/apache/trafficserver/tree/master/lib/atsc... You can do stuff like: > registerHook(HOOK_READ_REQUEST_HEADERS_PRE_REMAP); > registerHook(HOOK_READ_REQUEST_HEADERS_POST_REMAP); > registerHook(HOOK_SEND_REQUEST_HEADERS); > if (transaction.getClientRequest().getUrl().getQuery().find("redirect=1") != string::npos) { > cout << "Sending this guy to google." << endl; > transaction.getClientResponse().getHeaders().append("Location", "http://www.google.com"); > transaction.getClientResponse().setStatusCode(HTTP_STATUS_MOVED_TEMPORA