3 ms·

Quoting the comments section: The best possible way to achieve cacheability of an object is to perform a server-side re-write of all linked content (im

by Jakob 17y ago

Quoting the comments section: The best possible way to achieve cacheability of an object is to perform a server-side re-write of all linked content (images, scripts etc) and re-write the links to refer to a file name based off the MD5 hash of the file content. So, your link: http://us.i1.yimg.com/us.yimg.com/i/ww/beta/y3.gif is re-written: http://us.i1.yimg.com/never-expire/A31D5F12.gif Where A31D5F12 is the MD5 hash. Does somebody use this convention? It seems logical but I haven't seen it wildly used.

redorb 17y ago
Does this mess up what the new 'semantic web markup' movement is pushing? ... (I.e. google's image search uses the image name as a signal to what the image might be, albeit a small signal)
- lsb 17y ago
  It shouldn't, you can just have something like static.example.com/picture-of-cat-playing-piano-0123456789abcdef0123456789abcdef.jpg
- mahmud 17y ago
  Don't rewrite the URL completely, just append your session-data, caching hash and other metadata to the URL path.
wmf 17y ago
I first heard about this several years ago from a CDN; their proxy was automatically rewriting the links so the Web developer didn't have to do anything. I've never seen it used in the open source world.
ubernostrum 17y ago
I've seen it used, yes. I don't personally use MD5, but I've used variations based on modification timestamps.