Private Network Access - missing/different keys

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Private Network Access in HTTP Mixed Content was added in https://github.com/mdn/browser-compat-data/pull/23220

TargetAddressSpace was added in https://github.com/mdn/browser-compat-data/pull/22681

Both are related to the Private Network Access feature.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

There are at least two specific HTTP headers as part of PNA, which should be represented in http/headers (If I'm understanding BCD correctly):

• Access-Control-Request-Private-Network
• Access-Control-Allow-Private-Network

Unclear to me yet if:

• The mixed content bit is adjacent to the actual feature or part of it
• There are yet more keys as part of PNA

Did you test this? If so, how?

No

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

Start by reviewing the existing data under http/headers and the linked pull requests for Private Network Access and TargetAddressSpace. Determine which PNA headers and related keys belong in the compatibility data, then verify that their browser support matches the referenced sources.