LinkedData with TurboGears and squidDecember 3, 2008 at 6:33 pm | Posted in http, programming, python | 1 Comment
At work we run several TurboGears web applications, deployed behind Apache acting as proxy. I like this setup a lot, because it allows us to reuse our log file analysis infrastructure for the web applications as well.
Some of the web applications serve data that rarely changes, so to lower the traffic for TurboGears, I decided to use a transparent cache proxy. Since logging is already taken care of by Apache, I don’t care about not all requests hitting the application server.
Recently a new requirement came up: Serving Linked Data with these web applications. This is actually pretty easy to do with TurboGears. Creating RDF+XML with the templating engines works well, and even the content negotiation mechanism recommended for serving the data is well supported. To have TurboGears serve the RDF+XML representation for a resource just decorate the corresponding controller as follows:
TurboGears will pick the appropriate template based on the
Accept header sent by the client.
Unfortunately this setup – different pages served for the same URL – doesn’t work well with our squid cache. But the
Vary HTTP header comes to our rescue. To tell squid that certain HTTP request headers have to be taken into account when caching a response, send back a
Vary header to inform squid about this; thus, squid will use a key combined from URL and the significant headers for the cached page.
Now the only header important for our content negotiation requirement is the
Accept header, so putting the following line in the controller does the trick:
response.header['Vary'] = 'accept'