Context-aware HTTP caching (with Varnish) (opens in new tab)

I thought it was a great introduction to the topic. I found the jump to pre-authentication a little jarring, perhaps adding an explanation as to why caching logged-in users is a problem would help.

In the later examples, I don't think it's very clear that you're using the timestamps to show which responses are fresh and which are cached. Coloring the fresh/cached responses differently in the output might help.

Look forward to your next post.

White balance those photographs! Also you can make them much smaller with no apparent loss. http://i.imgur.com/EQulv.jpg

Excellent job... I think a second article in which you give specific examples of how Context-aware caching would work for a simple application would be helpful. Maybe a group chat service would be a great example. Also, adding HTTP requests within Varnish allows for a much more useful cache invalidation scheme... for example, incoming requests could have an content_token and timestamp. An internal HTTP service that records whether a given piece of content has expired (through user action rather than TTL) could then be checked before serving up a cached copy.

I think it's really good. One thing I'd change (not that I'm a good writer/blogger) is a clearer description in the first paragraph of why you'd want to do this.

"By using context aware caching, you can achieve high levels of caching for both anonymous and logged in users, unlike a dumb cache which generally excludes logged in user requests" or something like that.

Interesting as I'm not too familiar with Varnish. However it seems to me like it would be easier in many cases to pull out the session ID and then have a simple script which uses that to set the X-Auth-User header since most sites using authentication do so with session cookies.

It's just very good, please do continue. Also, the drawings are cool but that dark red is not contrasty enough with the number inside it, you might want to improve that for the upcoming posts. Keep up the good writing!

Yes, edge side includes are very interesting indeed! We used that for scenarios like you describe, but there are actually some things you should take into consideration when using them. Maybe I can dedicate a blog post to that! :)

Another option is to populate the cart preview via an ajax request, which allows the initial page to be served entirely from the cache.

I think it also depends on how you use Varnish. A lot of web applications can benefit from the reverse proxy capabilities of Varnish, but if you make Varnish part of your application stack from day one you can do things like I describe here. :)