Yep, I had an unpleasant experience today it seemed that the app.manifest was cached - I use this pr.
The customer is deploying on their setup - "luckily" they had messed up some ip adr and domains - I just found that my chrome remembered mixed routes and tried to load manifest from a completely different domain+protocol+port weird stuff - so chrome was looking the wrong place and the manifest load failed leaving the cached left - point, the appcache worked as it should.

The mozilla spec actually highlights in red that one should not include the manifest file in the app cache manifest - the browser handles this by it self - I'm not sure - it also highlights that instead of `?a=b` one should do `#something?a=b` havent tested this.

I havent got much time at the moment, but I would like to get this tested and extract some results on different platforms etc.