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, 8444 #24016
Add another https port, 8444 #24016
Conversation
44d8ce8
to
419d316
Compare
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
419d316
to
03c6936
Compare
I choose 8444 entirely arbitrarily. The Taskcluster failures are from stability checks timing out. The wpt.fyi browser results are just flake, I think. The Azure Pipeline failures seem a mixture of things... none obviously related to this PR. |
Ping @LukeZielinski are you able to review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the delay, this got buried in my inbox
This reverts commit 95cdf1f. Adding another HTTPS port broke both wpt.live (as its config no longer matched the number of ports asserted in wptserve) and the Chromium WPT Importer (as our pinned tooling failed to sub common/get-host-info.sub.js due to indexing out of bounds).
This reverts the change to common/get-host-info.sub.js in commit 95cdf1f. Adding another HTTPS port broke there broke the Chromium WPT Importer (as the pinned tooling failed to sub common/get-host-info.sub.js due to indexing out of bounds).
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