Extension blocked with HTTPS - Mixed Content about vscode-web HOT 3 CLOSED

Hi,
I'm glad you found the solution :)

If you need a dynamic scheme, to keep same codebase for localhost and deployed, you can use the dynamic version of product.json

By setting window.product variable, you'll be able to use javascript logic to define your product property

in your index.html or in any javascript file referenced:

const currentUrl = new URL(window.location.href);

window.product = {
...
 additionalBuiltinExtensions: [
    {
      scheme: currentUrl.protocol.replace(":", ""),
      path: "/myExt
    },
  ],
...
}

This use of product definition is quite powerful, for example it allows dynamic routing or defining custom commands without the extension sandbox

from vscode-web.

OK, I finally found out how to fix. 👍

I had to change the scheme under additionalBuiltinExtensions in product.json to https

  // ...
  "additionalBuiltinExtensions": [
    {
-      "scheme": "http",
+      "scheme": "https",
      "path": "/myExt"
    }
]

This, of course, won't work locally and has to be done in my deployment pipeline.

from vscode-web.

Changing the scheme under additionalBuiltinExtensions in product.json to https doesn't work for me.

But this works:

const currentUrl = new URL(window.location.href);

window.product = {
...
 additionalBuiltinExtensions: [
    {
      scheme: currentUrl.protocol.replace(":", ""),
      path: "/myExt
    },
  ],
...
}

@Felx-B Awesome thanks, you made my day

from vscode-web.