Support proxy to backend

[mmrath]

Issue #889

@filipesilva @TheLarkInn Here is the implementation for further discussion. I don't think it is merge ready. Please let me know your feedback on the implementation.

Also need your help on the testing side. How do I approach testing? Any existing test cases I can refer to?

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[mmrath]

I signed it!

[googlebot]

CLAs look good, thanks!

[mmrath]

I think we should remove proxy and insecure proxy options.

[filipesilva]

Can you include in the first comment a brief text description of your solution as well? It should help us review the code by giving it a overall summary.

In regards to testing I talked a bit with @TheLarkInn and one way that stood out was to have an additional server, proxy calls to it, and verify that we can get stuff from it. There might be better options but this one seemed sound.

[mmrath]

@filipesilva @TheLarkInn I have added two test cases, open for your review.

[TheLarkInn]

Need to update branch and tests will run again.

[mmrath]

@TheLarkInn Updated, all tests passed.

[allens]

@mmrath Thanks. I'm using your enhancement and it is working a well. It is essential for me, so it would be great to get this merged into the official branch soon.

Presumably the CI build will succeed now because of 5a9941e

[allens]

FWIW I agree about removing the proxy and insecure proxy options. They're pretty limited and are just adding to command line option overload.

[mmrath]

@filipesilva @TheLarkInn One of the travis CI run appears to be a flaky.

[filipesilva]

@TheLarkInn can you review?

[TheLarkInn]

LGTM pending tests.

[mmrath]

Thanks @TheLarkInn @filipesilva. All tests passed now.

[rogerfar]

@mmrath could you supply a bit of documentation for the readme? I've never worked with this and it's a bit confusing.

[filipesilva]

@yesman85 there is some documentation in the wiki: https://github.com/angular/angular-cli/wiki/stories-proxy

[nikithaperuka89]

@filipesilva I am having issues with my proxy.config it works locally. However, when I deploy the application to dev environment the backend api call fails with a 404.

Here is my proxy.config.json:

"/rest/": {
"target": "http://backend-api",
"secure": false,
"pathRewrite": {
"^/rest/": ""
},
"changeOrigin": true
}
}

package.json:
"scripts": {
"ng": "ng",
"start": "ng serve --proxy-config proxy.conf.json",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
}

Please advice

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