There's only one HTTPS port ({{ports[https][1]}} does not exist)
#17770
Comments
|
This seems like a reasonable and useful feature request. Not 100% sure about the cert setup: do we need to generate a new cert for the new port? cc @jugglinmike who recently played with SSL certs |
|
I'm not the person to speak authoritatively on certificate management, but on a purely anecdotal basis, it seems as though certs are port-agnostic. Another consideration is the memory consumption of a WPT server instance. Will running a fourth server (i.e. in addition to the existing two HTTP server and one HTTPS server) have a meaningful impact on WPT's overall resource requirements, relative to the available resources in consumers' automation infrastructure? |
|
Tentatively marking backlog, given lack of activity (and apparently lack of concern about said activity). |
In https://chromium-review.googlesource.com/c/chromium/src/+/1680096/, we're trying to verify behavior for a cross-scheme, same-host, cross-port fetch over HTTPS. That doesn't seem to be possible, as
{{ports[https][1]}}doesn't substitute to a port that works, which is unfortunate.Can we add a port? :)
/cc @anforowicz
The text was updated successfully, but these errors were encountered: