For a long time the Net panel wasn't able to handle the case when a network request comes directly from the browser cache (without any network communication with the server).
It was because of this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=449198 (this is now fixed but not available in FF3.0, which is still supported by Firebug 1.4) The way how the workaround works is to wait till the regular response comes or the request is found in the cache, which means "there won't be any response - it came from the cache already". This will be removed in FB 1.5 together with the warning that appears because of this hack. Honza On Jul 19, 12:56 am, HeHe <[email protected]> wrote: > FIREBUG WARNING: [Exception... "Component returned failure code: > 0x804b0044 (NS_ERROR_CACHE_IN_USE) [nsICacheSession.openCacheEntry]" > nsresult: "0x804b0044 (NS_ERROR_CACHE_IN_USE)" location: "JS frame :: > chrome://firebug > > my FF is 3.5. > > my FB is 1.4.0. > > thanks!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
