UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce the problem:
Given an acceptance testing environment composed of:
- a "selenium/standalone-chrome" container ready to launch a Chrome instance
- containers under test (e.g. Django apps running LiveServerTestCase)
it is cumbersome to test web apps containing "Powerful New Features" requiring a secure origin.

The reason is that the webdriver (ChromeDriver) is meant to be initialized once, before the testing begins (e.g. [1]), and during the testing, the web application is restarted for every test case, and so is exposed on different ports because of TIME_WAIT state on the previous one [2]. This means that it is impossible to provide a proper origin for "--unsafely-treat-insecure-origin-as-secure" (when there are no domains configured).

[1] https://behave.readthedocs.io/en/latest/tutorial.html#fixtures
[2] https://docs.djangoproject.com/en/1.11/releases/1.11/#liveservertestcase-binds-to-port-zero

What is the expected behavior?
Allow the Remote ChromeDriver access the web application under test no matter under which port it will be available.

This feature request is about supporting the "*" wildcard in any combination of (scheme, host, port) provided to "--unsafely-treat-insecure-origin-as-secure" (and the OverrideSecurityRestrictionsOnInsecureOrigin policy).

What went wrong?
I can't test my Service Worker.

Did this work before? No 

Chrome version: Version 71.0.3578.98 (Official Build) (64-bit)  Channel: stable
OS Version: 
Flash Version: