Open Bug 1300796 Opened 5 years ago Updated 4 years ago

When call to nsICacheEntryOpenCallback.onCacheEntryCheck throws, carry the error to status of onCacheEntryAvailable


(Core :: Networking: Cache, defect, P5)




Tracking Status
firefox51 --- affected


(Reporter: mayhemer, Unassigned)


(Whiteboard: [necko-would-take])

When an implementer of nsICacheEntryOpenCallback forgets to implement onCacheEntryCheck in JS, the status it gets in onCacheEntryAvailable is NS_ERROR_CACHE_KEY_NOT_FOUND, which may be pretty confusing, specially when using OPEN_NORMAL flag.  Carrying the error to OCEA may help identify this problem more quickly.
Bulk change to priority:
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.