1823921 - Filter out some requests from ORB telemetry

Status: RESOLVED FIXED

(Core :: DOM: Networking, enhancement)

Description

[Sean Feng [:sefeng]]

I think before we start to collect more data, the simplest thing we can do is to follow Olli's suggestion by filtering nsIContentPolicy::TYPE_BEACON, nsIContentPolicy::TYPE_PING and nsIContentPolicy::TYPE_CSP_REPORT requests out from the ORB telemetry probes, since the content process will do nothing to these requests so having them blocked by ORB should have zero web-compat concerns.

Especially for TYPE_BEACON because Amazon.com and live.com both have ORB blocked requests with TYPE_BEACON.

Comment 1

[Sean Feng [:sefeng]]

Attachment: Bug 1823921 - Filter out some types of requests from the ORB_DID_EVER_BLOCK_RESPONSE probe r=farre,smaug

Content processes can do nothing to the responses of nsIContentPolicy::TYPE_BEACON,
nsIContentPolicy::TYPE_PING and nsIContentPolicy::TYPE_CSP_REPORT requests, so filter
them out of the ORB_DID_EVER_BLOCK_RESPONSE probe to not worry them for
web compatibility.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

One thing we need to figure out is how to not show these loads as errors in the devtools network monitor.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d9c64e620b71
Filter out some types of requests from the ORB_DID_EVER_BLOCK_RESPONSE probe r=farre,necko-reviewers,kershaw

Comment 4

[Sean Feng [:sefeng]]

One thing we need to figure out is how to not show these loads as errors in the devtools network monitor.

Filed bug 1824137

Comment 5

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/d9c64e620b71