Suborigins

Provides a mechanism for a server to specify a new origin for a page to run in that is named and contained within the same physical (scheme/host/port) origin. For example, an application running at https://google.com/foo which the server places in the Suborigin namespace Foo will run in a new origin based on the tuple (https, google.com, 443, Foo). This would be considered a different origin space from (https, google.com, 443) or (https, google.com, 443, Bar)

Documentation

Specification

Editor's draft

Status in Chromium

Blink


No active development (tracking bug)

Consensus & Standardization

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

  • No signal
  • No signal
  • No signal
  • Mixed signals

Owner

Last updated on 2020-10-25