Expose whether trr was used to nsHttpChannel
Categories
(Core :: Networking: DNS, enhancement, P3)
Tracking
()
People
(Reporter: dragana, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][trr])
We want to know if only trr is used:
- not-trr dns response was used
- a trr response was used but a native dns query has been sent as well
- only trr request has been sent.
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
I'm working on patches for some of this in bug 1525640.
Can you explain a bit more what we want to use that info for? Just telemetry?
|
|
||
Updated•6 years ago
|
|
|
Reporter | |
Comment 2•6 years ago
|
||
(In reply to Valentin Gosu [:valentin] from comment #1)
I'm working on patches for some of this in bug 1525640.
Can you explain a bit more what we want to use that info for? Just telemetry?
maybe for a future shield study if we have one and maybe for dev-tools
|
|
||
Comment 3•6 years ago
|
||
(In reply to Dragana Damjanovic [:dragana] from comment #0)
We want to know if only trr is used:
- not-trr dns response was used
- a trr response was used but a native dns query has been sent as well
- only trr request has been sent.
I posted the patches in bug 1525640. I'm still working on a test. It only exposes if the request used a TRR IP or not (doesn't say if we fall back to regular DNS etc), and it also doesn't say if the original request used TRR and we just loaded it from the cache (might be relevant in split horizon situations).
Let's use this but for future improvements.
|
||
Updated•5 years ago
|
|
||
Updated•2 years ago
|
Description
•