Closed
Bug 69731
Opened 23 years ago
Closed 23 years ago
GetUriSpec() incompatible to GetCachedNetData()
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
VERIFIED
FIXED
mozilla0.9
People
(Reporter: c, Assigned: gordon)
Details
In nsCacheManager::GetCachedNetData() a "\n" is used to separate a secondary key from the URI spec, but in nsCachedNetData a "\0" is expected. If I read "uriSpec" I get both the URI spec and the secondary key, separated by a "\n". getSecondaryKey() tries to read beyond the string and leads to random errors (most time NS_OUT_OF_MEMORY, but maybe that could cause a crash). The same problem occurs in nsAboutCache::DumpCacheEntries(). Example: var a= NDCM.getCachedNetData( "URI", "secondary", 9, 0 ); alert( a.uriSpec ); // shows "URI\nsecondary"
Will be resolved when new cache lands
Assignee: neeti → gordon
Target Milestone: --- → mozilla0.9
Comment 2•23 years ago
|
||
closing this per new cache landing
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•