deployUrl not bound correctly

[es-lab]

OS?

macOS Sierra

Versions.

@angular/cli: 1.0.0-rc.1
node: 7.7.1
os: darwin x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9

Repro steps.

Build with ng build -prod -deploy-url=http://sub.domain.com/.
In css files the links for images/fonts/etc.. are set like this: /http:/sub.domain/com/assets/....
The browsers tries to load the following url: http://domain.com/http:/sub.domain/com/assets/...

Mention any other details that might be useful.

My assets and every additional file but the index.html are served from http://sub.domain.com/ because of my backend. When I was using version beta26, setting deployUrl=http://sub.domain.com/ worked for files inside the index.html (but not for the favicon, this is an issue still in rc1, please put the deployUrl for the favicon too!). There were still issues with imgs, and other assets, a workaround was loading them through css, but this worked only if loading them in the style that was loaded form the subdomain, images loaded from inline style still failed.
Now with rc1 I see that you put the deployUrl in styles too, this is good, but it works only for path prefixes, not entire hosts like in my use case.

[filipesilva]

Heya, I'm fixing the deployUrl behaviour with a full URL on #5372.

Regarding favicon, that's up to you to configure really... it's just listed in index.html, and you can change it.

[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.}