You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As just noticed when trying to get a test with Cross-Origin-Opener-Policy added, the url fixture (which other fixtures like inline are based on) defaults to HTTP. That means we basically don't test anything for HTTPS right now, which is IMO a huge deficit.
Switching the default to HTTPS raises another question. How can we get a valid certificate added to the certificate store of each browser to not have to enable the acceptInsecureCerts capability? As @jgraham pointed out for Firefox it will be easy soon when his patch series from PR #28729.
The problem of a trusted certificate is already solved since stuff like https://web-platform.test:8443 is used while running lots of testharness.is tests.
I have almost no experience with the WebDriver tests in WPT so I don't know if that setup is easy to reuse, or perhaps if it's already in use.
github: web-platform-tests/wpt#28847
jgraham_ (IRC): WPT in general uses http as the default. THis doesn't match the web anymore
… this is not going to impact the webdriver so much
… so we should move that to be more like the web
automatedtester: as long as we still make sure that we test misconfigured servers then I don't see this being an issue
jgraham: that will be fine
As just noticed when trying to get a test with
Cross-Origin-Opener-Policy
added, theurl
fixture (which other fixtures likeinline
are based on) defaults to HTTP. That means we basically don't test anything for HTTPS right now, which is IMO a huge deficit.Switching the default to
HTTPS
raises another question. How can we get a valid certificate added to the certificate store of each browser to not have to enable theacceptInsecureCerts
capability? As @jgraham pointed out for Firefox it will be easy soon when his patch series from PR #28729.But how does it look like for other browsers?
CC'ing @foolip, @burg, @JohnChen0, @bwalderman.
The text was updated successfully, but these errors were encountered: