let's have: timestamp,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5 this is controlled with "logging.<module_name>" = <level> preferences. P2 as this positively influences convenience of all external bug reports analyzes.
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Attachment #8933715 - Flags: review?(valentin.gosu) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/f848a44b2868 Update about:networking#logging default list of logs to a more useful list, r=valentin
Comment on attachment 8933715 [details] [diff] [review] v1 Since this may really help when diagnosing networking related bugs, I'd like to get this to at least Beta (if there is a plan for 57 dot release, it would be nice to take these as well) Approval Request Comment [Feature/Bug causing the regression]: none [User impact if declined]: two steps when asking for logs (first w/o important modules, second with "please modify the list as bla bla and do again") [Is this code covered by automated tests?]: n/a [Has the fix been verified in Nightly?]: yes! manually [Needs manual test from QE? If yes, steps to reproduce]: n/a [List of other uplifts needed for the feature/fix]: none [Is the change risky?]: no [Why is the change risky/not risky?]: just changes a default value of a field on a diagnostic page, zero user impact otherwise [String changes made/needed]: none
Attachment #8933715 - Flags: approval-mozilla-beta?
Note: related MDN document has been updated.
Comment on attachment 8933715 [details] [diff] [review] v1 For help diagnosing networking related bugs. Beta58+.
Attachment #8933715 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.