When we first built Widget 2.0, we set it up to take a relative URL protocol (beginning with //).
We've had a couple customers who needed to be able to explicitly specify this as https:// in the widget embed code.
We've updated the logic so that it still uses the relative protocol by default but will also accept https: added to the start of the _ko19.base_url.
