New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 555117 link

Starred by 11 users

Issue metadata

Status: Duplicate
Merged: issue 336894
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Task


Show other hotlists

Hotlists containing this issue:
EnamelAndFriendsFixIt


Sign in to add a comment

Suborigins namespace mechanism

Project Member Reported by jww@chromium.org, Nov 12 2015

Issue description

Change description:
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.

Changes to API surface:
* Suborgin header to specify a page's entry into a suborigin
* Access-Control-Allow-Suborigin response header
* New event.suborigin field

Links:
Public standards discussion: https://lists.w3.org/Archives/Public/public-webappsec/2014Nov/0127.html
Editor's draft of spec: https://metromoxie.github.io/webappsec/specs/suborigins/

Support in other browsers:
Internet Explorer: no signals
Firefox: no signals
Safari: no signals
 

Comment 1 by jww@chromium.org, Nov 12 2015

Note that  issue 336894  has been tracking actual development of the feature.

Comment 2 by mmi...@gmail.com, Dec 8 2015

I opened a ticket in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1231225

Comment 3 by jww@chromium.org, Dec 8 2015

Thanks for the support! Make sure to follow along on public-webappsec mailing list (https://lists.w3.org/Archives/Public/public-webappsec/), too.

Also, as an update to this thread, the Editor's Draft is now here:
https://w3c.github.io/webappsec-suborigins/
https://github.com/w3c/webappsec-suborigins/issues/
Owner: jochen@chromium.org

Comment 6 by owe...@chromium.org, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

Comment 7 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt
Mergedinto: 336894
Status: Duplicate (was: Assigned)

Sign in to add a comment