Speaking of finally, I wonder when they're going to add proper support for "Content-Encoding: gzip". Last I checked, people would upload gzipped content and add the Content-Encoding header on top, which is inconvenient and doesn't support browsers that can't handle gzipped responses.

Honest question: which browsers can't handle gzip'd responses?

IE6 has problems with cached Gzip files: basically it forgets they're Gzipped in the cache and then drops the Content-Encoding part of the file. So it loads garbage as far as the JS interpreter is concerned.

I've had issues with gzip and wget, though I don't know if that was just a mis-configured site or something (and wget isn't a browser).

I definitely want this feature as well. But I feel like it won't happen for a while because to make this happen Amazon incurs additional overhead for caching the gzipped version.

I'd like to reinforce the "finally". This has been requested on the AWS forums for years.

However, the fact that AWS crushes entire business models with every move they make relativizes their slow pace somewhat.

And I wouldn't say they're slow, on the contrary. They've been adding features to AWS like clockwork for like 6 years now. Every few months, they add something that a large amount of people love. And then it just works. That's awesome. They're running a marathon, not a sprint, and doing awesomely well so far.