Closed
Bug 367257
Opened 18 years ago
Closed 9 years ago
images requested 3+ times when browser.cache.memory.enable is set to false
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: justincwatt, Unassigned)
Details
Attachments
(1 file)
47.68 KB,
patch
|
Details | Diff | Splinter Review |
When browser.cache.memory.enable is set to false and an image is loaded directly in the browser, e.g. http://www.google.com/intl/en_ALL/images/logo.gif, the file will be requested three (or more) times. You can confirm the three separate HTTP GET requests using the LiveHTTPHeaders extension. Tested in FF v2.0.0.1.
This is minor, probably affects no one, and doesn't not appear to be a problem when loading an HTML page in the browser which references the same images, e.g. http://google.com/ but it is weird---and maybe it points to something weird going on.
Updated•18 years ago
|
Component: File Handling → Networking: Cache
Product: Firefox → Core
QA Contact: file.handling → networking.cache
Version: 2.0 Branch → 1.8 Branch
Comment 1•18 years ago
|
||
I just tested with LiveHTTPHeaders 0.13.1 and Firefox 2.0.0.4 for OS/2 and don't see this problem. There is only one GET.
Ah, wait. If I also set browser.cache.disk.enable to false then I do see it. Also on trunk.
OS: Linux → All
Hardware: PC → All
Version: 1.8 Branch → Trunk
Reporter | ||
Comment 2•18 years ago
|
||
OS/2? Wow.
Comment 3•18 years ago
|
||
I got curious and set a breakpoint in nsHttpTransaction::Init() to see where the three calls come from. This file shows that the calls for an image inside a HTML file go across nsHTMLImageElement and only call imgLoader::LoadImage() once. The standalone image is loaded via JavaScript and nsDocShell (once, load in the end initialized using nsURILoader::OpenURI()) and nsXULElement (twice, load initialized using imgLoader::LoadImage()).
Not sure what all this means though...
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•