We have a separate submission path and controlling prefs for SSL error reporting: https://dxr.mozilla.org/mozilla-central/rev/095988abdc560bf8ba07a94a425c6922a3e9bfd6/browser/base/content/browser.js#2823 https://gecko.readthedocs.org/en/latest/browser/base/sslerrorreport/index.html We should consider submitting them through Telemetry, which now comes basically down to e.g.: > TelemetryController.submitExternalPing("ssl-error", reportObject, options) This lets it use a common send implementation, local persistence, feed through our common datapipeline, ... and we could make it obey global datareporting upload preferences.
Or is that what the CertViolation ping in bug 1120377 is about?
This is all the same thing, yes. They went ahead with something else for cert violations earlier, but now we should use the common system.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1120377
You need to log in before you can comment on or make changes to this bug.