Jeremy Morton wrote:
> I must be misunderstanding something here. What is HTTP data if it is
> not things like images downloaded from websites, and cached pages?
An "image" can be one of two things in Mozilla:
1) The raw bytes downloaded via some network protocol like HTTP.
2) The bitmap that results once those raw bytes have been decoded
from whatever compressed image format they're in (JPEG, GIF,
PNG, etc).
Data from category 1 is cached in either the disk or memory cache (depending on
HTTP vs HTTPs), if it's cached at all, and is subject to both the HTTP protocol
pref and the cache prefs.
Data from category 2 is cached in a separate memory cache device and is subject
to the memory cache pref only.
> "WYCIWYG [...] is a URI scheme specific to the Mozilla family of web
> browsers which indicates that a link should be preferentially fetched
> from cache instead of from the web server."
Uh... wherever you found that documention needs to be fixed. It's wrong.
wyciwyg is what's used to make it possible to go back/forward through history
across document.open/document.close calls. When document.open/write/close is
used to create a document, that document is cached (either on disk or in memory
depending on whether the JS caller is http or https). This caching is not
subject to the HTTP pref, but is subject to the cache prefs.
-Boris
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
