ng serve not working behind reverse proxy basehref/servepath

[everflux]

Command

serve

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

before vite

Description

I provide remote training for Angular using VSCode in the browser.
It is no longer possible to use the vscode port forwarding to access the ng dev server as basehref and servepath combinations to not yield the correct result when @angular node resources are to be loaded. It works for all other assets/files in the project.

Minimal Reproduction

Use code-server oder vscode server access through web browser.

ng new
ng serve --host 0.0.0.0 --disable-host-check

Open the forwarded port, URL becomes f.e.
https://student01.remote-training.de/proxy/4200/

Exception or Error

No response

Your Environment

Angular CLI: 17.3.6
Node: 20.12.2
Package Manager: npm 10.5.0
OS: linux x64

Angular: 17.3.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.6
@angular-devkit/build-angular   17.3.6
@angular-devkit/core            17.3.6
@angular-devkit/schematics      17.3.6
@angular/cli                    17.3.6
@schematics/angular             17.3.6
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.5

Anything else relevant?

I tried various configuration combinations using prebundle, basehref and servepath only to experience worse problems like beeing redirected to https://student01.remote-training.de/proxy/4200/proxy/4200/

[everflux]

What is the outcome of the investigation? Is there something I can help with?

[taoyouh]

I've seen similar problem (#29139). Vite seems to be adding your base href before all hrefs starting with / (like /some-link), but the relative hrefs (like some-link will remain untouched and work as expected. I fixed the issue by removing all the / prefix in my index.html. My other templates are using router-link and they just works.

[exasky]

I've seen similar problem (#29139). Vite seems to be adding your base href before all hrefs starting with / (like /some-link), but the relative hrefs (like some-link will remain untouched and work as expected. I fixed the issue by removing all the / prefix in my index.html. My other templates are using router-link and they just works.

Unfortunately, this doesn't work behind a reverse proxy, it only adds 'XXX/YYY' to all paths
In my case, I use code-server, and putting 'proxy/4200' instead of '/proxy/4200' doesn't solve the issue