6 ms·

Article from 2007

• oniTony 15y ago
  2008+ version -- throw your assets into CloudFront (or another CDN of choice), let CDN handle the caching. ;)
  • mkchandler 15y ago
    I know you say that in jest, but I would say that it is still good to know the underlying technology. It is much easier to debug issues in the future once you understand them.
    • bitops 15y ago
      Concur - I think that, once you have a certain amount of experience built up working in frameworks like Rails, you can only go so far before you hit a wall. At that point, it's necessary to start learning the protocols and the lower level stuff to advance your understanding and your craft.
• bittermang 15y ago
  Good information doesn't necessarily have an expiration date, but I concede to your point that it might not be the most up to date source out there.
• kalid 15y ago
  Yep, I was surprised too to see it on HN :). I think one of the meta-takeaway is that understanding the fundamentals of web caching can help with your general CS knowledge ("There are only two hard problems in Computer Science: cache invalidation and naming things." -- Phil Karlton). Looking at Apache, we see a few strategies: * Include last-modified metadata * Include content metadata (eTag/md5 of content) * Include explicit expiration date * Include a max-age * Include metadata about who can cache (public/private/no-caching, i.e. users can cache but proxies cannot) These approaches could be used when designing data flows with Memcache, Redis, etc.
  • SquareWheel 15y ago
    One thing I don't understand. If the server has asked the client to cache an image for a year, and the image is indeed updated in that time, is there some way of telling the client to download that image anyway? I'd take it to Google, but I have no idea how I'd ask that in Google query form.
    • pork 15y ago
      In HTTP, since it's stateless, you don't "tell" the client anything without it first asking. The usual way to bust the cache is to add a junk parameter to the end of a GET request.
      • SquareWheel 15y ago
        I see. I assume you would change the html code to say <img src="image.png?cache=no"> or something like that to force the browser to redownload it? What if the html page itself were cached for a year? Is there an Apache setting that can give a global "no caching" command, or something like that?
        • kalid 15y ago
          Yep, exactly -- not only can the images be cached, but the HTML too! The ideal way to do it is have the "loader file" (index.html) only cached with last-modified date, so as soon as it changes the client is aware. The client requests the file each time, and is returned the full file or a simple Not Modified response. Within the file, you have references to permanently-cached, versioned resources (<img src="/images/foo.png?build=123" />). If the cache expiration is far enough away, the browser won't even issue the request to check for a new version. Some browsers don't cache query params so you might use rewriting rules to change foo.png to foo.123.png. This rewriting is done automatically for you with Google Page Speed module for Apache.
          • SquareWheel 15y ago
            It sounds like a much deeper subject than I first appreciated. I'll definitely read up on this. Using URL rewriting with caching is interesting, I've not seen that before. I work with one lady that complains about a slow loading JQuery slideshow, and smarter caching may very well be the solution (at least, after the first load).