Hi Yiewi,

I don't know the exact answer to your question, but my assumption is that it would not be possible to set the cache value to infinite for two reasons:

• Your hard drive has a finite size, so technically, it would not be possible to have an infinite cache.
• For the above reason, I assumo that those settings probably expect a finite number

You can, instead, set it to a very large number. Is there a particular reason why you wish to do this? I believe the cache has diminishing returns, so setting it to a extremely large number would have very little or unnoticeable improvements over a standard cache.

Regarding your Firefox 16.0 version, please be advised that you are using an outdated version of the browser that has many security flaws. It is highly advised that you update your browser to the latest version (through this link) for many security and performance improvements.

We hope that this answers your questions. Please let us know if you have any other questions.

Thanks!!

- Ralph

Thanks, rjbd.

No, that is not possible.

We set a lower bound of 50MB and an upper bound of 1GB.

• http://mxr.mozilla.org/mozilla-central/source/netwerk/cache/nsCacheService.cpp#607

Oh, so that means even I set the cache to 9999999 it still won't work?

The reason why I want this extremly large cache is because I'm using some large data from localstorage and in my javscript I write something like localStorage.a = localStorage.a + "some information", so I though it needs to first read the old value of localStorage.a into the cache, append the "some information" and then store it back to localStorage.a. However, this localStorage.a is very big(probably 900GB). Or am I totally wrong that the old value won't go to the cache? Thanks!

LocalStorage is not the same as the disk cache.

• https://developer.mozilla.org/en/DOM/Storage

You can consider to use IndexedDB (offline cache) to store a large amount of data locally.

• https://developer.mozilla.org/en-US/docs/IndexedDB

Thanks for the help, cor-el! But still if I use this indexedDB instead of localStorage, if in my javascript I have indexedDB.a = indexedDB.a + "some value", will this old value of indexedDB.a still go through the cache that has upper bound of 1GB? (since I think it is similar to var temp = indexDB.a; indexDB.a = temp + "some value")

If yes, I still couldn't solve the problem that if my indexedDB.a is very big, then the limitation on the cache won't allow me to append new value to it.