CUNY Academic Commons

We go to lots of trouble to append a custom 'ver' querystring for CSS and JS assets, for the purposes of busting these files as cached by browsers. But we depend on the browsers to decide when and whether to cache these assets in the first place. We should instead be explicit: the files should be cached as aggressively as possible.

I'm going to drop some Expires headers into 1.9.1 and see if anything breaks :-D If not, we should see some immediate and fairly dramatic performance boosts, at least for those clients (read: desktop browsers) that are less aggressive about asset caching.