Closed
Bug 1817761
Opened 2 years ago
Closed 2 years ago
Key telemetry differently when using OHTTP
Categories
(Core :: Networking, enhancement, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
We need to add a "ohttp-cloudflare" and maybe "ohttp-other" key to the list of providers and change the call to SetProviderDomain to check if it's currently using ohttp.
|
Assignee | |
Comment 1•2 years ago
|
||
For our initial experiment we'll be using the dooh.cloudflared-dns.com
domain for our resolver.
We probably should key things separately for OHTTP, but for now this
should be enough to capture the telemetry we are interested in.
|
||
Updated•2 years ago
|
Assignee: nobody → valentin.gosu
Status: NEW → ASSIGNED
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/87c5e6e6e220
Key telemetry differently when using OHTTP r=necko-reviewers,kershaw
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•