Remote source path given 404 error when working http://127.0.0.1:8080/vscode url

[e-vural]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome 133.0.6943.142
• Local OS: Macos Sonama 14.4
• Remote OS:
• Remote Architecture:
• code-server --version: v4.98.0 and also main branch

Steps to Reproduce

1. Open code-server in chrome with http://127.0.0.1:8080/vscode
2. Open chrome developer console
3. You can see 404 errors

Expected

Proper functioning of extensions

Actual

This error causes the extensions not to work correctly. The php files look like txt because the extension is not working.

In my investigations, http://127.0.0.1:8080/vscode/vscode/oss-dev/vscode-remote-resource?path=. I saw that extra /vscode was added in this url. lib/vscode/src/vs/base/common/network.ts If I change the code in line 224 to this._remoteResourcesPath, there seems to be no problem. But I don't know if the problem is only caused by this.

Logs

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

No, this works as expected in GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

No response

[code-asher]

Does the same problem happen if you browse to http://127.0.0.1:8080 (no /vscode)? /vscode is a legacy route, but we should fix it all the same.

[code-asher]

Or, wait, is /vscode something you added with a reverse proxy? If that is the case, I think http://127.0.0.1:8080/vscode/ (trailing slash) should work.

[e-vural]

Or, wait, is /vscode something you added with a reverse proxy? If that is the case, I think http://127.0.0.1:8080/vscode/ (trailing slash) should work.

Yes! You are right. http://127.0.0.1:8080/vscode/ that url working. However, I use the same configuration in v4.96.4. There is no problem in that version. v4.98.2 has problems. is this normal?

[code-asher]

Hmm that does seem strange, I would expect previous versions to have the same problem without a trailing slash.