sockjs-node url is ignoring the 'pathname' part of the publicHost

[sherif-elmetainy]

🐞 Bug report

Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: 8.0.6

Description

Running the command ng serve --public-host http://myhost.example.com/mypath cause the URL for loading sockjs-node script to ignore the /mypath (i.e. the pathname part) of the public host URL.

🔬 Minimal Reproduction

Run the command
ng serve --public-host http://myhost.example.com/mypath
Open the browser to the app URL and check the outgoing requests in network tab in developer tools

As the problem is not related to app code, any app created with ng new with default settings should be fine to reproduce the problem.

🔥 Expected Behaviour

Calls to sock-nodejs should look like this:
http://myhost.example.com/mypath/sockjs-node/info?t=123456

🔥 Actual Behaviour

The actual URL looks like this:
http://myhost.example.com/sockjs-node/info?t=123456

🌍 Your Environment

Angular CLI: 8.1.0
Node: 10.15.0
OS: win32 x64
Angular: 8.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.0
@angular-devkit/build-angular     0.801.0
@angular-devkit/build-optimizer   0.801.0
@angular-devkit/build-webpack     0.801.0
@angular-devkit/core              8.1.0
@angular-devkit/schematics        8.1.0
@ngtools/webpack                  8.1.0
@schematics/angular               8.1.0
@schematics/update                0.801.0
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

Anything else relevant?
This was working fine in 8.0.6. Updating to 8.1.0 (using ng update) caused the problem. Reverting back to 8.0.6 solves the problem.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}