Limit "external requests" to secure contexts.

Requires that external requests may on be initiated from a secure context. "External requests" are those initiated from a public network, targeting a private network. Examples include internet to intranet requests and intranet loopbacks.

Servers running inside local networks, or on a user's device, expose powerful capabilities to the web in ways that can be quite dangerous. CORS-RFC1918 proposes a set of changes to limit the impact of requests to these servers by ensuring that the servers are opting-into any communication with external entities. For this opt-in to have any meaning, the servers need to be able to ensure that the client origin is authenticated. To that end, only secure contexts are empowered to make external requests. This change is separable from the rest of CORS-RFC1918, and we can make it now, before the rest of the larger feature is ready.

Specification

Editor's draft

Status in Chromium

Blink


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Mixed public signals
  • No public signals
  • No public signals
  • Negative

Owner

Last updated on 2019-07-24