Comments on: twitter! http://dom.as/2009/03/25/twitter/ Sat, 17 Dec 2011 20:14:59 +0000 hourly 1 http://wordpress.com/ By: twitter! « domas mituzas: vaporware, inc. | Twitter Kid http://dom.as/2009/03/25/twitter/#comment-1544 Mon, 30 Mar 2009 22:24:21 +0000 http://dammit.lt/?p=436#comment-1544 [...] original post here:  twitter! « domas mituzas: vaporware, inc. Posted in Articles | Tags: 2009-at-2143, amazon, browser, europe, expires, firefox, march-26, [...]

]]> By: Marco http://dom.as/2009/03/25/twitter/#comment-1543 Sun, 29 Mar 2009 19:43:37 +0000 http://dammit.lt/?p=436#comment-1543 Thank you for the expiration date hint, but a lot of traffic is produced via API and not just the web interface. xD

]]> By: Saliem http://dom.as/2009/03/25/twitter/#comment-1542 Thu, 26 Mar 2009 21:04:32 +0000 http://dammit.lt/?p=436#comment-1542 is that why you don’t have a twitter account? :D

]]> By: Justin Lintz http://dom.as/2009/03/25/twitter/#comment-1541 Wed, 25 Mar 2009 23:46:56 +0000 http://dammit.lt/?p=436#comment-1541 Including an ETag won’t do much of anything if they have an Expires and max-age already set. With just an ETag set , anytime a repeat visitor hits a page with a static asset already cached, it will send a INM request, and the server will respond with a 304. If you have just the expires or max-age set, the browser won’t even re-validate the object, it will just serve from the browser cache, saving on some bandwidth.

I don’t think adding public to cache-control would affect anything either as that IIRC just makes http authenticated responses cachable.

]]> By: Domas Mituzas http://dom.as/2009/03/25/twitter/#comment-1540 Wed, 25 Mar 2009 23:04:20 +0000 http://dammit.lt/?p=436#comment-1540 well, we use Vary at Wikipedia a lot, and it doesn’t seem to be causing any caching problems (as long, as we handle the remaining set of headers properly).

]]> By: Josh Davis http://dom.as/2009/03/25/twitter/#comment-1539 Wed, 25 Mar 2009 22:56:29 +0000 http://dammit.lt/?p=436#comment-1539 The culprit here must be the Vary header. Most browsers interpret it as “Cache-control: must-revalidate” no matter what other headers you sent with. In fact, I’ve just tested twitter.com on my Firefox 3.0.7 and the CSS files don’t even seem to be cached at all.

]]> By: Tomas Markauskas http://dom.as/2009/03/25/twitter/#comment-1538 Wed, 25 Mar 2009 22:11:22 +0000 http://dammit.lt/?p=436#comment-1538 They could at least use Amazon’s CloudFront as a CDN which is so easy to implement. Proper timestamps for assets would probably save them more than a lunch in data transfer fees :)

]]>