Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
Make sure port forwarding for 8080 is automatically added and assigned a https://*.asse.devtunnels.ms/ URL.
Expected: VS Code opens https://*.asse.devtunnels.ms/test in my browser
Observed: VS Code opens https://*.asse.devtunnels.ms/ in my browser
STR2:
in terminal in VS Code, run echo http://127.0.0.1:8080/mypath/
Make sure port forwarding for 8080 is automatically added and assigned a https://*.asse.devtunnels.ms/ URL.
Ctrl+click the above link from stdout in terminal
Expected: it opens https://*.asse.devtunnels.ms/mypath/ in browser
Observed: it opens https://*.asse.devtunnels.ms/ in browser
Above is just a minimal example. A real scenario: I sometimes run
>snakeviz event.prof
snakeviz web server started on 127.0.0.1:8080; enter Ctrl-C to exit
http://127.0.0.1:8080/snakeviz/D%3A%5Ctemp%5Cvimeo%5Cevent.prof
404 GET / (127.0.0.1) 2.00ms
(404'd because VS Code automatically opens https://*.asse.devtunnels.ms/ instead of https://*.asse.devtunnels.ms//snakeviz/D%3A%5Ctemp%5Cvimeo%5Cevent.prof in my browser; and it's very confusing)
STR1:
https://*.asse.devtunnels.ms/
URL.Expected: VS Code opens
https://*.asse.devtunnels.ms/test
in my browser Observed: VS Code openshttps://*.asse.devtunnels.ms/
in my browserSTR2:
echo http://127.0.0.1:8080/mypath/
https://*.asse.devtunnels.ms/
URL.Expected: it opens
https://*.asse.devtunnels.ms/mypath/
in browser Observed: it openshttps://*.asse.devtunnels.ms/
in browserAbove is just a minimal example. A real scenario: I sometimes run
(404'd because VS Code automatically opens
https://*.asse.devtunnels.ms/
instead ofhttps://*.asse.devtunnels.ms//snakeviz/D%3A%5Ctemp%5Cvimeo%5Cevent.prof
in my browser; and it's very confusing)