Caching and headers

[eluser]Aquillyne[/eluser]
You'll have to remind me what DRY stands for.

You're right, this is just the important bit from Suffix cache. But actually the problem you've highlighted has nothing to do with this. It's a problem already present in the CI core. Without the additions I've made, your problem will still crop up (and with them too); indeed, these additions don't even address that problem, Suffix cache does (per title).

My additions fix the problem one step along the way. If both index.css and index.js both have caching enabled, currently in CI one will overwrite the other. The next time you load index.css you'll get the JavaScript. All my additions will do will make that JavaScript come along with a "text/javascript" Content-Type header (if you'd set it).

In other words, the problem you've described is actually two problems: the lack of cached headers, and the lack of suffix recognition. Suffix cache solves both. My addition solves just one (the caching of headers). Neither causes the problem you're describing. CI has been causing that one on its own.