Note that Private Network Access is in the process of being renamed to Local Network Access, so you may see inconsistent names for the time being.
Allow same-origin local network fetches to potentially-trustworthy origins and do not send preflights for them. We currently send preflights before all local network requests, but ignore the results, as proposed in Intent to Ship: Private Network Access preflight requests for subresources.
We haven’t been able to enforce the preflight results for private network requests because the compat risk is still too high. See this thread for discussions about the compat risk involved.
Preliminary metric data in dev and beta show that by excluding same-origin requests, we can reduce the number of ignored warnings by ~2x. Reducing the compat risk gets us closer to start enforcing the preflight results.
Added an FYI comment about this change.
This change reduces the compatibility risk of enforcing preflight results on private network requests as we now send fewer preflights for private network requests, so it’s less likely to break websites.
Gecko: No signal about this specific change.
WebKit: No signal about this specific change.
Web developers: No signal about this specific change, but they should be happy since this reduces compatibility risks.
We plan to ship this change directly as this relaxes the previous restrictions.
This change is limited to potentially trustworthy origins. Proof of certificate protects users from DNS rebinding.
There’s no plan to ship Local Network Access on WebView.
Relevant information (client and resource IP address space) is already piped into the DevTools network panel.
Only for metric logging
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/PrB0xnNxaHs/m/jeoxvNjXCAAJ
Intent to Deprecate and Remove: Private Network Access requests for subresources without proper preflight response: https://groups.google.com/a/chromium.org/g/blink-dev/c/FlenxUPCDec/m/FNJ0wCmKBAAJ
This intent message was generated by Chrome Platform Status.