Scoped Rule Storage

[puff-m-d]

Hello,

I am having an issue of scoped rules reverting back to a previous version that I am trying to troubleshoot. I am assuming when you commit rules that they are cached somewhere. My reasoning for this is the following scenario: I have committed new scoped rules in HTTPSB. I then close my browser and clear caches and temp files. The next time I open my browser, the newly committed rules are not there and the scoped rules have reverted to the previous set that I had prior to committing. Most of the time if I reboot my machine without clearing the caches and temp files, the rules will then be remembered and are now "set". I feel fairly sure that when I clean my caches and temp files, I am deleting something that I should not, but for the life of me I cannot figure it out. In order for me to troubleshoot and fix this issue, I need to know where these scoped rules are being stored (both actual location and the cached location if one exists). I can then be sure these are excluded from deletion in the future thus hopefully solving my issue as I am pretty sure the problem is on my end with the clearing of caches and temp files, and not an issue with HTTPSB. Any help in knowing the files and their locations would be greatly appreciated as I have been trying to figure this out for a while now with no success on my own. Thanks in advance...

P.S. I had a similar issue with HTTPS Everywhere but that was easy to fix as I found it saved its user rules in C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Local Storage and not in C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings as what I would have thought. HTTPSB does not seem to store anything in the C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Local Storage location though...

[puff-m-d]

FYI: When trouble shooting this I did find two extensions identified as: eemcgdkfndhakfknompkggombfjjjeno and pafkbggdmjlpgkdkcbjmhmfcdpncadgh showing up in C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Local Storage that I could not identify as to what extensions they belong to. I only have added three extensions to Chrome: uBlock, HTTPSB, and HTTPS Everywhere and these do not appear to be related to them. Deleting them both from "local storage" does not seem to have an effect on anything as far as I can tell and does not appear to be related to my HTTPSB issue. I am just curious as to what extensions those two files belong to...

[gorhill]

The chrome.storage.local API is used: https://developer.chrome.com/extensions/storage

For the two other extensions, look at their manifest files, there should be enough information in it to figure what they are. There are built-in extensions/apps by Google, even in Chromium, so I would think Chrome has even more.

[puff-m-d]

Hello gorhill,

Thanks for the reply and help. After reading the link you posted (remember that I am not a programmer and most of it was above my head), I am assuming the chrome.storage.local API does its thing in memory and saves this information to either one or both of the following folders: C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Extensions\mghdpehejfekicfjcdbfofhcmnjhgaag C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings\mghdpehejfekicfjcdbfofhcmnjhgaag So if nothing is being deleted from these two folders, in theory I should have no issue. I have 100% verified these folders are not touched when I clear my caches and temp files but the issue remains. Is there somewhere else that this information is being stored or am I just missing something?

As to the other two extensions, they must be part of Chrome as they do not exist in the "Extensions" folder. The only reference to them is in the "Local Storage" folder. I am not really worried about them as I was only curious as to where they came from.

Thanks for your help and you can consider this closed as a non-issue (was only for informative and learning on my part).

[gorhill]

How do you clear cache and temp files?

[puff-m-d]

Hello gorhill,

I use programs for this depending on the situation (for example - quick cleaning, daily cleaning, cleaning before imaging, in depth monthly cleaning, etc.). i have just done individual testing on my different methods trying to pinpoint it to one program causing it but during this test it did not happen. I have gone over logs of what was deleted when the issue occurs and cannot find anything that was deleted that had anything to do with HTTPSB.

This is not a major issue at the moment (since uMatix is on the horizon), Since HTTPSB is soon to be replaced by uMatrix, I am not going to worry about it further. I will wait till the first release of uMatrix to revisit this and see if it occurs again. It only happens 2, maybe 3 times a week, so no big deal. I always keep a back-up of HTTPSB up to date to restore just in case.

Thanks very much for your time and help. I am always eager to learn...