Ah, right. In most cases, this won't be an issue, I doubt users with /bigfile.mov would care /bigfile.mov/something to be a useful URL. That said, I agree it is not very neighborly to have the behavior change unexpectedly when the file size gets too big.

What if we gave users a way to explicitly opt files out of the cache, and just documented that this affected subpaths too? Then, even though the behavior is the same, it is what the user expects. Something like `Meteor.AppCache.skipFiles('/bigfile.mov')`. Then the warning could explicitly call out the code you need to fix the problem (like the autopublish warning tells you how to disable autopublish).