[Level
T2]
Browsers are very sophisticated HTTP machines. We often fail to remember how much of the HTTP spec is implemented by the browsers.
As I have said before, ASP.NET Web API is a very powerful server-side framework but there is a
client-side burden in using it or generally implementing a RESTful system - although Web API does not restrict you to a RESTful style.
Because of the client burden, we need more and more client-side libraries to implement lacking features that browser have had for such a long time - one of which is HTTP caching. If you use
HttpClient out of the box, it will not implement any caching even though the resources are cacheable. Also all of the work for conditional GET or PUT calls (using
if-none-match, etc) or cache validation (if there is
must-revalidate) or checking whether your cache is stale has to be done in your own code.
CacheCow is an HTTP caching library for client and server in ASP.NET Web API that does all of above - see my
earlier post on that. Storage of the cache is abstracted in
ICacheStore and for now we can use in memory implementation (see below). So the features in the client library include:
- Caching GET responses according to their caching headers
- Verifying cached items for their staleness
- Validating cached items if must-revalidate parameter of Cache-Control header is set to true. It will use ETag or Expires whichever exists
- Making conditional PUT for resources that are cached based on their ETag or expires header, whichever exists
Today I released v0.1.3 of the CacheCow.Client on
NuGet. This library would implement advanced HTTP caching with little or no configuration or hassle. All you have to do is to add the CachingHandler as a delegating handler to your HttpClient:
var client = new HttpClient(new DelegatingHandler()
{
InnerHandler = new HttpClientHandler()
});
This code will create an HttpClient that implements caching and stores the cache in memory. By implementing
ICacheStore, you can store the cache in your custom repository. CacheCow is going to have persistent cache stores such as
FileCacheStore,
SqlCeCacheStore and
SqliteCacheStore as a minimum.
FileCacheStore will be similar to browser implementation of cache storage. Each of these cache stores will be implemented and released under its own NuGet package. To add an alternative cache store, you need to pass the store as a constructor parameter.
Usage
So in order to use, CacheCow.Client, use package manager in Visual Studio to download and add reference to it:
PM> Install-Package CacheCow.Client
This will also download and add reference to ASP.NET Web API client package, if you have not already added a reference to. Make sure try v0.1.3 or above (by the time of reading this).
After this you just need to create an
HttpClient as above and add the
CachingHandler as a delegating handler. That's it, you are ready to call services and cache the responses!
Sample
I am working on a sample project but for now, it is easiest to use the code below to call my CarManager Azure website which implements HTTP Caching. The code can be pasted from
this GitHub gist.
CacheCow.Client adds a special header to the response which helps with debugging its various features. The header's name is
x-cachecow and has a various flags on the operations done on the request/response. So in the code below, we will use this header to demonstrate the features of this library.
var client = new HttpClient(new CachingHandler()
{
InnerHandler = new HttpClientHandler()
}
);
var initialResponse = client.GetAsync(
"http://carmanager.azurewebsites.net/api/Car/5").Result;
var initialResponseHeader = initialResponse.Headers.Single(
x => x.Key == CacheCowHeader.Name).Value.First();
Console.WriteLine(initialResponse.Headers.ETag.Tag);
Console.WriteLine(initialResponseHeader);
And we will see this to be printed:
"02e677a7799e484fb49447f8a600247d"
0.1.3.0;did-not-exist=true
As you can probably figure out, we have the ETag and the
CacheCowHeader: first value is the version and did-not-exist means that item did not exist in the cache - which is understandable as this is the first call.
Now let's try this again:
var secondResponse = client.GetAsync("http://carmanager.azurewebsites.net/api/Car/5").Result;
var secondResponseHeader = secondResponse.Headers.Single(
x => x.Key == CacheCowHeader.Name).Value.First();
Console.WriteLine(secondResponseHeader);
And what will print is:
0.1.3.0;did-not-exist=false;cache-validation-applied=true;retrieved-from-cache=true
So in fact, it existed in the cache, retrieved from the cache and cache validation was applied. Cache validation is the process by which client makes conditional call to retrieve/update a resource only if the condition is met (see Background section in
this post). For example, in GET calls it will send the ETag with a
if-none-match header to retrieve
If you call a PUT on a resource that is cached, CacheCow.Client will use its ETag or Expires value to make a conditional PUT, unless you set
UseConditionalPut property to false.
By-passing caching
There are some cases where you might not want the result be cached or retrieved from the cache regardless of the caching logic. All you have to do is to set the
CacheControl header to
no-cache or
no-store:
var nocacheRequest = new HttpRequestMessage(HttpMethod.Get,
"http://carmanager.azurewebsites.net/api/Car/5");
nocacheRequest.Headers.CacheControl = new CacheControlHeaderValue()
{
NoCache = true
};
var nocacheResponse = client.SendAsync(nocacheRequest).Result;
var nocacheResponseHeader = nocacheResponse.Headers.FirstOrDefault(
x => x.Key == CacheCowHeader.Name);
Console.WriteLine(nocacheResponseHeader);
This will print an empty header since we have by passed the caching.
Last but not least
Thanks for trying out and using CacheCow. Please send me your feedbacks and bugs. Just ping me on twitter or use GitHub's issue tracker.
