I store user-uploaded images in the Google App Engine datastore as db.Blob
, as proposed in the docs. I then serve those images on /images/<id>.jpg
.
The server always sends a 200 OK
response, which means that the browser has to download the same image multiple time (== slower) and that the server has to send the same image multiple times (== more expensive).
As most of those images will likely never change, I'd like to be able to send a 304 Not Modified
response. I am thinking about calculating some kind of hash of the picture when the user uploads it, and then use this to know if the user already has this image (maybe send the hash as an Etag
?)
I have found this answer and this answer that explain the logic pretty well, but I have 2 questions:
- Is it possible to send an
Etag
in Google App Engine? - Has anyone implemented such logic, and/or is there any code snippet available?
By the way, thanks to webob, webapp.RequestHandler provides easy way to check If-None-Match.
why would the code use this:
instead of this:
I think it is the same and will use the 2nd unless someone explains the reasoning.
Bloggart uses this technique. Have a look at this blog post.
There might be a simpler solution here. This requires that you never overwrite the data associated with any identifier, e.g. modifying the image would create a new id (and hence a new URL).
Simply set the
Expires
header from your request handler to the far future, e.g. now + a year. This would result in clients caching the image and not asking for an update until that time comes.This approach has some tradeoffs, like ensuring new URLs are embedded when images are modified, so you have to decide for yourself. What jbochi is proposing is the other alternative that puts more logic into the image request handler.