When a page matching a fallback namespace could not be load (e.g. doesn't exsist) we load the fallback resource for this page (as expected) but when this fallback document loads, based on conditions of cache selection algorithm it invokes cache update with reference to the non-existing page. We try to load the page a second time. IMHO, we should not invoke the update at all even the spec doesn't explictily say we shouldn't.

I have to recheck this bug and then fix it close it as invalid.

(In reply to comment #1) > I have to recheck this bug and then fix it close it as invalid. Honza, I can't quite parse that. Is it two sentences or missing some words?

It should be: - I have to check this bug still exists (there were some changes that might fix this as I remember) - Then, I have to fix it if we still believe it is a problem or just close it as WONTFIX Anyway, this is a very low priority bug.