Comment 2 for bug 710562

I've changed expires to be 30mins, instead of "max"

I've never had complaints for basic assets such as css/js/etc. for maximum cache expiry - html can be an issue though I suppose since docs are created with that extension.

I can also just make it so .html is treated normally and the rest are still expires max. Typically if you want to force refresh assets like javascript or css, msot people use "cache busting" mechanisms - cheating the system by query string.

Etags shouldn't be required necessarily. nginx doesn't support them natively and "last modified" should work properly.

nginx doesn't natively support deflate either. Is it that important?

If these are that limiting, I suggest we just wind up moving to Apache, but there should be no reason nginx can't fit the bill. I've hosted rpm repos on nginx, dynamic sites and static sites. Typically all with heavy expires headers (at least for assets) - the .html extension seems like the only possible difference or issue here.