Remote - Tunnels does not forward to localhost when using VS Code client

VS Code version info for client:
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

VS Code version information for host:
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

Remote - Tunnels extension version: v1.6.2023110809

Steps to Reproduce:

1. Create a Dev Box or another machine that is running Windows
2. Install VS Code and Remote - Tunnels on this host
3. Sign-in to Remote - Tunnels using a GitHub ID on this host, use Turn Remote Tunnel Access On, and select the option to keep it running as a service
4. On your client machine, install the Remote - Tunnels extension, in VS Code cleint (not web) sign in, and connect.
5. Forward a port from your client

Expected: Port is forwarded to localhost
Actual: Port is forwarded via a HTTPS url

This cuts off general TCP access, and any web application going through Oauth will have to continually update valid callback URIs. Typically people use localhost to avoid this problem.