Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add another HTTPS port #23579

Closed
domenic opened this issue May 13, 2020 · 2 comments · Fixed by #24016
Closed

Add another HTTPS port #23579

domenic opened this issue May 13, 2020 · 2 comments · Fixed by #24016

Comments

@domenic
Copy link
Member

domenic commented May 13, 2020

I'd like to test that two different-port-same-host origins can be isolated from each other using origin isolation. Since this is a HTTPS-only feature, this requires two separate HTTPS ports.

Web platform tests only provides one, thus preventing me from writing these tests :(.

Some draft tests that fail for trying to access an out-of-bounds {{ports[https][1]}} at https://chromium-review.googlesource.com/c/chromium/src/+/2199550

stephenmcgruer added a commit that referenced this issue Jun 5, 2020
This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes #23579
stephenmcgruer added a commit that referenced this issue Jun 17, 2020
This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes #23579
stephenmcgruer added a commit that referenced this issue Jun 17, 2020
This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes #23579
stephenmcgruer added a commit that referenced this issue Jun 29, 2020
This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes #23579
@stephenmcgruer
Copy link
Contributor

Sadly the js part of this was reverted in #24394 due to breaking Chromium's importer. What we need to do is roll the tooling into Chrome, and only then re-land the js part.

@stephenmcgruer stephenmcgruer self-assigned this Jun 30, 2020
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue Jul 3, 2020
Automatic update from web-platform-tests
Add another https port (#24016)

This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes web-platform-tests/wpt#23579
--

wpt-commits: 95cdf1fdf4b4e82ee53edbe43f3f260f28f07bd6
wpt-pr: 24016
xeonchen pushed a commit to xeonchen/gecko that referenced this issue Jul 6, 2020
Automatic update from web-platform-tests
Add another https port (#24016)

This is required to test origin isolation
(https://github.com/WICG/origin-isolation), which includes guarantees
that two origins with the same host but different ports are treated as
isolated.

Fixes web-platform-tests/wpt#23579
--

wpt-commits: 95cdf1fdf4b4e82ee53edbe43f3f260f28f07bd6
wpt-pr: 24016
@sparkleholic
Copy link

sparkleholic commented Aug 11, 2021

@domenic

two different-port-same-host origins can be isolated from each other using origin isolation. Since this is a HTTPS-only feature, this requires two separate HTTPS ports.

For HTTP, is origin-isolation not possible depending on the port?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants