Does `getServerProductSegment` function not work in `out-vscode-reh-web`?

[Cecil0o0]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: a forked version
• OS Version: Darwin arm64

Steps to Reproduce:

1. npm run minify-vscode-reh-web until the task is done successfully
2. node ./out-vscode-reh-web/server-main.js until the server is started successfully
3. some resources whose scheme of FileUri is vscode-remote-resource://, the server is handle /vscode-remote-resource, however, workbench UI sends a request with a path started with '/oss-{{commitId}}', which results in an error File is not found. But if the request is started with /vscode-remote-resource, I promise that it would work.

[bpasero]

Looks like @aeschli added this 5 months ago, to support running behind a Proxy, can you please check?

vscode/src/vs/base/common/network.ts

Lines 234 to 236 in 2c4a398

	export function getServerProductSegment(product: { quality?: string; commit?: string }) {
	return `${product.quality ?? 'oss'}-${product.commit ?? 'dev'}`;
	}

[aeschli]

Can you debug here and see why the path is not handled?

vscode/src/vs/server/node/remoteExtensionHostAgentServer.ts

Line 129 in cc60f14

if (pathname.startsWith(this._serverProductPath) && pathname.charCodeAt(this._serverProductPath.length) === CharCode.Slash) {

[Cecil0o0]

With added breakpoint at the line 64867 of the bundled server-main.js, as displayed below, I found the pathname of the current problematic request is started with /oss-{hash-long-string}/vscode-remote-resource, but the expression this._serverProductPat is '/oss-dev' which is mismatch with prior, so the path is not handled