Hi,
The sqlite files used by CEF/chrome can be read with a DB browser, and answer #2 in this StackOverflow post seems to say that for Windows the encryption used for some values can be cracked by another program on the same PC: http://stackoverflow.com/questions/2253 ... -in-chrome
In other words, someone could run a program on the dbs in the cache folder and extract at least cookies, maybe more.
Privacy: person A could snoop on person B's activities using a cache folder reading app.
Security: This is our use case. We need to prevent users from spoofing our application (by reading cookies) and from doing a view source of some HTML pages on servers that we do not control. We also don't want them to be able to "see" some URLs by inspecting the history.
A post last year by someone else asked about disabling caching, but they never gave you a reason why and the thread went without an answer to how to accomplish it: viewtopic.php?f=6&t=11661
So, is there any way to disable caching in the client, as opposed to on the server? The only cache mentions I see in the sample client are ways to have the request ignore existing cache entries, and the setting for the cache folder which (when left empty) still creates the cache folder in the user's temp folder.