Growing Communicator cache Test.
JavaScript seems to be a reason for that growth. Maybe there are more.
The link => Click here
to go to this same page
Each time you click on the link, a new file is added to cache directory.
About:cache let us see what's hapenning. Each click creates a different
entry in the cache. This is one of them:
URL: wysiwyg://5/http:...test2.html
Content Length: 1464
Content type: text/html
Local filename: MU28JEB1.HTM
Last Modified: No date sent
Expires: No expiration
date sent
It has a especial identifier, wysiwyg, and
a special number for each entry, 5 in this case. As they have
not Last Modified Date, these files are erased when you close Communicator...
if all goes well.
The Back button doesn´t bring the previous
page
The Back and Forward buttons is caotic (at this moment, and for me)
with the files above mentionated if they are in the hard disk.
-
Copy this page to the Temp directory
-
Go to other URL (url1) at a navigator
window
-
Go to C:\Temp\test2.html. Note that Navigator transforms the URL to file:///C|/Temp/test2.html
-
Click several times the HERE link (above in this page), and then click
Back button.
-
The browser backs to the previous page at this window, url1.
-
Click Forward and note the URL location.
-
Resize the window. Oops, the URL is changed => file:/C|....
-
Click the HERE link again (a new file is added)
-
Click Back
-
It shows this same page, but writing a new hour (then is not using one
of the cache copys, or is it?).
-
Click Forward ... a new hour (to use or not to use?)
-
Click Back ... a new hour (at least, this back and ford game, doesn´t
create files at cache directory)
-
Click Forward ... a new hour
-
...
There are two copys of the file in the cache and Communicator is not using
any of them. It is generating the page always.
-
A last glance: open Communicator History
-
Sort by last modified
-
Yes, there are two entries at history for this page
-
Click back and ford.