Not working for subdmains - blocked by chrome/firefox because of http instead of https

[rimvislt]

When loading from xxx.test toolbar links are using https but when using domain admin.xxx.test debug toolbar is using http for loading assets and both browsers chrome and firefox are now blocking by default under https loading http.

SERVER_NAME: 'xxx.test'
PREFERRED_URL_SCHEME = "https"

register subdomain blueprint
app.register_blueprint(
bp,
url_prefix='/',
subdomain=admin
)

Firefox URL https://admin.xxx.test
Blocked loading mixed active content "http://xxx.test/_debug_toolbar/static/js/jquery.js"
home
Loading failed for the <script> with source “http://xxx.test/_debug_toolbar/static/js/jquery.js”. home:239:1
Blocked loading mixed active content "http://xxx.test/_debug_toolbar/static/js/jquery.tablesorter.js"
home
Loading failed for the <script> with source “http://xxx.test/_debug_toolbar/static/js/jquery.tablesorter.js”. home:240:1
Blocked loading mixed active content "http://xxx.test/_debug_toolbar/static/js/toolbar.js"
home
Loading failed for the <script> with source “http://xxx.test/_debug_toolbar/static/js/toolbar.js”.

Chrome URL https://admin.xxx.test
Mixed Content: The page at 'https://admin.xxx.test/login' was loaded over HTTPS, but requested an insecure script 'http://xxx.test/_debug_toolbar/static/js/jquery.js'. This request has been blocked; the content must be served over HTTPS.
login:1 Mixed Content: The page at 'https://admin.xxx.test/login' was loaded over HTTPS, but requested an insecure script 'http://xxx.test/_debug_toolbar/static/js/jquery.tablesorter.js'. This request has been blocked; the content must be served over HTTPS.
login:1 Mixed Content: The page at 'https://admin.xxx.test/login' was loaded over HTTPS, but requested an insecure script 'http://xxx.test/_debug_toolbar/static/js/toolbar.js'. This request has been blocked; the content must be served over HTTPS.

[jeffwidman]

Myself or one of the other maintainers are happy to review a PR if you want to put one up tackling this.

[macnewbold]

I agree, if this is still an issue, I'm happy to review a pull request that would correct it.