Open sp00n opened 8 years ago
Hi @sp00n,
Is there anything more I could try?
Yes, you could use RP's log.
extensions.requestpolicy.log
to true
(on about:config
)If you could do that, it will help me a lot in resolving this issue.
Hm. How would it work in Linux?
Hm. How would it work in Linux?
firefox > log.txt
Okay, in windows it's the ">" character as well [source], so try this command:
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" > log.txt
log.txt
is the log file.
Ok, so I tried that now, but the resulting log file is just empty. The config flag for RP is also set to true. I also tried the -console and -attach-console command line parameters as described here, but they didn't seem to do anything either (with or without the dump into log file switch).
Try to start firefox with the -console
option [stackoverflow].
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -console > log.txt
After installing the keepa.com addon for Amazon, I can't get it to work. I know it did work a couple of months ago, but I don't remember exactly when it stopped doing so.
I've tried to add the various addresses requested by the addon to the rules section (i.e. *.keepa.com, cdn.keepa.com, keepa.com), but it didn't work, and moreover none of these entries even show up in the request log.
The curious thing is however that I was able to make it work (and make the addresses show up in the log) when I a) disable the addon, restart the browser, and enable the addon again. or b) set the addon to "Disable blocking" (yellow flag), and restart the browser.
This is the only time when it is working. After another restart it's back to the default non-working state.
Tried it on both Firefox 48.0.1 and 49.0.1. System is Win7 x64, RP version is 1.0.beta12.3.
Is there anything more I could try?