Logfile
Re: Logfile
You can enable more logging by setting extensions.logging.enabled to true. However, this will go to the Error Console (or possibly Browser Console), rather than to a file.
A log of all blocked requests would soon grow ridiculously large.
A log of all blocked requests would soon grow ridiculously large.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0
Re: Logfile
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
-
David44
Re: Logfile
Yes, but diskspace is not the problem. With compression less than ever.Thrawn wrote:A log of all blocked requests would soon grow ridiculously large.
Do I understand correctly, only requests are logged and not the blocked requests? So it might be not so helpful as I wish.barbaz wrote:https://addons.mozilla.org/firefox/addo ... st-logger/ ?
If there's no built in capability or other ideas, maybe it's possible to merge the http-request-logger in noscript. After a quick look: the function openConsole seems to be the right place. But time is missing...
Opera/9.52 (X11; Linux i686; de)
Re: Logfile
It will log all outgoing requests but not those that are blocked by nsIContentPolicy implementations which do their thing before that addon even sees the requests.
I think the only reliable way to log all blocked requests, would be to modify every single addon you got so that when they block a request, they send (via custom observer notifications) data about that request to some custom addon that writes all data it gets to a file. You would also have to re-apply your changes with every addon-update. Not something I'd want to do, but YMMV..
I think the only reliable way to log all blocked requests, would be to modify every single addon you got so that when they block a request, they send (via custom observer notifications) data about that request to some custom addon that writes all data it gets to a file. You would also have to re-apply your changes with every addon-update. Not something I'd want to do, but YMMV..
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24