tickbox: log every request performed by the browser (for manual inspection)
tickbox: clear logfile at sessionstart (else it is appended, and grows huge)
Ideally, on each line the logfile would indicate the scheme, as well as the URL.
Logfile would be comprehensive ~~ each request is logged, regardless how it is initiated (user click, URL of embedded asset, html canvas toDataUrl() operation, xhttp/json request/ javascripted POST or PUT, etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, the good news are that I have already done some basic logging stuff for next release. Currently it won't save the log to file because writing to disk is a slow operation (many pages do hundreds of request). That can be helped with SSD or ramdisk however.
I do however add option for logging to file too and by default this logging operation will disabled so to not slow things down when you don't want to debug whats going on behind your back when surfing.
Also, right now it can be also used for viewing images and maybe more in the future (could be used to grabbing and saving even YouTube videos in the future)
I might release this logging stuff as separate patch before actual release
of CD 1.6.5.
Added file logging widgets and options for logging date/time, action and MIME Type. Url is of course always logged to file. Also for 200 OK http replies it will color code the line with green and for >= 400 wiht red.
It now shows images as well as any text/* MimeType.
Will release next week as an patch to 1.6.4, I am after all on vacation now.
Last edit: Stefan Fröberg 2014-08-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, when active, that addon "churns" my HDD if multiple tabs containing ajaxy-goodness are loaded.
I believe it hooks/observes the window.loaded() event. IOW, one write per document... plus I don't know how often following an xhttp request
It would be sensible to buffer the writes, updating file on disk only "every XXminutes" or after accumulating XXkb in the buffer... but, on many occasions (crashes) the instantaneous writes have enabled me to sort out "what the Hell just happened? Why the crash?"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Separately (further down the road) it would be great to have the ability to marshall (intercept, inspect, optionally block) requests of selected type(s).
At a given moment, during a given session... yes, maybe I do want to inspect the content of imminent xhttp requests ~~ might not be easily human-readible, but I would have opportunity to view it (prior to its https encryption, vs MITM proxy wireshark or for forensic examination)
In the near-term, on-demand ability to disable any "silent" requests would be a welcome feature addition.
tickboxes: [ ] allow xhttp (json/ajax) requests [ ] allow http POST requests
Last edit: sandax 2014-08-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
tickbox: log every request performed by the browser (for manual inspection)
tickbox: clear logfile at sessionstart (else it is appended, and grows huge)
Ideally, on each line the logfile would indicate the scheme, as well as the URL.
Logfile would be comprehensive ~~ each request is logged, regardless how it is initiated (user click, URL of embedded asset, html canvas toDataUrl() operation, xhttp/json request/ javascripted POST or PUT, etc.
Well, the good news are that I have already done some basic logging stuff for next release. Currently it won't save the log to file because writing to disk is a slow operation (many pages do hundreds of request). That can be helped with SSD or ramdisk however.
I do however add option for logging to file too and by default this logging operation will disabled so to not slow things down when you don't want to debug whats going on behind your back when surfing.
Also, right now it can be also used for viewing images and maybe more in the future (could be used to grabbing and saving even YouTube videos in the future)
I might release this logging stuff as separate patch before actual release
of CD 1.6.5.
https://www.dropbox.com/s/ednxjeh8vevsrc8/InitialLoggingFeatureForCyberDragon.png
Update: This is how it looks now.
https://www.dropbox.com/s/tf8rk1kbkelhy37/CyberDragonLogger2.png
Added file logging widgets and options for logging date/time, action and MIME Type. Url is of course always logged to file. Also for 200 OK http replies it will color code the line with green and for >= 400 wiht red.
It now shows images as well as any text/* MimeType.
Will release next week as an patch to 1.6.4, I am after all on vacation now.
Last edit: Stefan Fröberg 2014-08-01
feature-wise, this is nearly exactly what I had in mind:
https://addons.mozilla.org/en-US/firefox/addon/http-request-logger/
Yes, when active, that addon "churns" my HDD if multiple tabs containing ajaxy-goodness are loaded.
I believe it hooks/observes the window.loaded() event. IOW, one write per document... plus I don't know how often following an xhttp request
It would be sensible to buffer the writes, updating file on disk only "every XXminutes" or after accumulating XXkb in the buffer... but, on many occasions (crashes) the instantaneous writes have enabled me to sort out "what the Hell just happened? Why the crash?"
Separately (further down the road) it would be great to have the ability to marshall (intercept, inspect, optionally block) requests of selected type(s).
At a given moment, during a given session... yes, maybe I do want to inspect the content of imminent xhttp requests ~~ might not be easily human-readible, but I would have opportunity to view it (prior to its https encryption, vs MITM proxy wireshark or for forensic examination)
In the near-term, on-demand ability to disable any "silent" requests would be a welcome feature addition.
tickboxes:
[ ] allow xhttp (json/ajax) requests
[ ] allow http POST requests
Last edit: sandax 2014-08-04
PATCH_CyberDragon_1.6.4_Logger_and_other.zip now adds logger to CD 1.6.4.
installed the patch & returned to post a new thread
"feedback regarding initial version of the Prefs--}Logger tab"
sf page didn't offer "general discussion" in the selectbox
and
upon posting, display "your post is awaiting moderation".
Maybe my sf login cookie timed out? Maybe that post will show up as "posted by anonymous"?
========
edit: didn't see "post awaiting moderation" msg when I posted this so, yeah, probably due to a dropped cookie
Last edit: sandax 2014-08-05
It has appeared to "features that you need badly" forum.