-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log about:transparancy to console/file #71
Comments
Hi, The transparency page just shows a summary of outgoing requests from the browser. Depending on how much detail you want, you can also just monitor the HTTP traffic directly. The easiest way to do this is via the extension debugger: visit From the dev tools you can export to HAR format for further analysis. |
Ah, true. For these messages, I think @philipp-classen may be able to advise on how to see the original content on these messages. I'll also take this issue on-board as a feature request for an 'audit' mode for exporting all communicate with Cliqz' backend. The current dashboard is somewhat limited. |
Logging to a file or stdout when an environmental variable is set would suffice. Or logging to the browser console while the about:transparancy is open.
Displaying the last 10 minutes of data instead of the single last data point would be an enormous improvement. Maybe show the last by default but with an expander toggle to show last ten minutes? Instructions on how to log to a file would also suffice. |
@da2x You can make log outputs visible to print the unencrypted messages before they are sent. The steps are described in our blog post on Human Web (at the end): There is also a pref, which you can flip to turn off encryption at all. However, that means the proxy can also see (or could modify) your traffic, so reserve that option only for testing. |
grimm jr.
|
Hi, can I somehow output a log of what goes on in about:transparency? There are delays before activity shows up, and things disappear before I get a chance to look at it.
The text was updated successfully, but these errors were encountered: