1. Álvaro Justen - Turicas
  2. web2itter
  3. Issues
Issue #1 new

Turn web2itter cache friendly

Kurt Kraut
created an issue

Since the content provided by web2itter is not expected to truly change on each HTTP request, the page should tell browsers, search engines and web caches(like Squid) when a certain page is expected to change. This could be achieved by two meta tags: {{{

!html

<meta http-equiv="cache-control" content="public"> <meta http-equiv="expires" content = "Mon, 14 set 2009 11:12:01 GMT"> }}}

So, if the refresh rate are set to 30 seconds, the meta tag EXPIRES should show a GMT time when the next refresh is expected (e.g.: last refesh time + 30 Seconds). Please note that RFC 2068 specifies that HTTP time expressions should be in GMT.

This would speed up the user experience (since content can be reliably cached) and save server resources (bandwith, RAM and processing) without introducing any kind of outdated information in the web page display.

Comments (0)

  1. Log in to comment