Closed
Description
Hello,
it appears, as if maybe #11657 broke the path-based port forwarding inside VS Code Web.
The env var VSCODE_PROXY_URI was constructed correctly in v2.6.0 and before.
Expected Behavior
VSCode starts with the correct env var VSCODE_PROXY_URI for path-based VS Code like this:
https://coder.example.com/@USER/test.instance/apps/code-server/proxy/{{port}}
Actual Behavior
If I start a web app in the workspace the automated port forwarder in VS Code constructs a URL for a subdomain based app, like:
https://{{port}}--instance--test--USER.coder.example.com/
Since subdomain based routing is not an option for us, this breaks our VS Code setup.
Steps to Reproduce the Problem
- Setup template like described in documentation here
- Switch to a path based app in template
- Start workspace from template
- Start VS Code browser
- Start web application in VS Code
Specifications
- Version: v2.7.1
- Platform: Linux
- Subsystem: Ubuntu 22.04
Metadata
Metadata
Assignees
Labels
No labels