Static File Introspection and Debugging about turtledove

[dmdabbs]

• See whether Chrome has tried to download a delegation file (in general or just for the current page).

Before they plumbed many of these browser-issued background requests to DevTools, Network, one had to resort to a NetLog dump, https://www.chromium.org/for-testers/providing-network-details/. Well-known delegation requests should be listed there and whether it was serviced from cache.

I'm curious about the same things for the attestation file,

There's an intent to bundle the attestations file with Chrome. See https://issues.chromium.org/issues/40942169.

[MattMenke2]

It looks to me like PA's .well-known network fetches are not currently hooked up to devtools. Bidder/seller scripts and signals files are. Unfortunately, the way things work in Chrome, how and where requests are made affects whether they're logged to devtools. We have added code to wire up all requests made from the worklet process, but we have not added hooks specific to .well-known file fetches.

.well-known fetches are, of course, available in about:net-export (which includes all requests made globally), though that's not a great solution.