That's true, but

1) this happens after rack::cache does its work
2) I think it's the only way to make sure public pages don't get cached for signed in users

I think I should modify that pull to allow caching of assets, unless discourse does something non-standard there? Would it be safe to cache everything in /assets/* for signed in and signed out users?