angular-cli@webpack option --proxy does not work

[wz2b]

The '--proxy' option does not work - or at least does not work the same as it did with the systemjs version. For example, I can run:

ng serve --proxy http://example.com

and request using Http:

http.get("/api/xyzzy").suscribe( xxxx );

and I can see it makes a request of the local server but the local server returns the application entry page (index.html).

This version of angular-cli calls out:

"ember-cli": "2.5.0"

which calls out:

"http-proxy": "^1.9.0",

and I have verified that both these are present at those versions.

Linux - Ubuntu 14,04
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.2.1
os: linux x64

[zsfarkas]

It seems to be [closed.] #1487 -> I am hoping to get it soon...

And there is a hack if you want to use the latest beta (webpack.2): #1712

[jandsu]

It seems Angular CLI 1.0.0-beta.11-webpack.9-4 is mixing up --proxy and --proxy-config options:

$ ng serve --proxy https://foo.bar.com
Proxy config file /home/me/code/app/https:/foo.bar.com does not exist.

[filipesilva]

It doesn't work in the same way, no. You can see some documentation in #1896, it's going to be merged soon.

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