Pass through entire path when proxying

[tstirrat]

When using the http-proxy blueprint, a proxied request does not pass through the full path. e.g.

ember g http-proxy api http://localhost:5000
ember serve

http://localhost:4200/api/foo - [proxied] -> http://localhost:5000/foo # unexpected

http://localhost:4200/api/foo - [proxied] -> http://localhost:5000/api/foo # expected

It looks like it is not going to be supported in node-http-proxy since they removed "proxy table" support: http-party/node-http-proxy#386

The fix is simple.

[tstirrat]

This PR doesn't cover it, but do you see value in handling complex cases when a path is specified in the destination?

e.g.

ember g http-proxy api http://localhost:5000/api/v1

http://localhost:4200/api/foo - [proxied] -> http://localhost:5000/api/v1/foo

ember g http-proxy foo http://localhost:5000/bar

http://localhost:4200/foo/123 - [proxied] -> http://localhost:5000/bar/123

[rwjblue]

If someone needs that level of customization, we should simply encourage they edit the generated file to add it.

[trek]

I'd like some more discussion around this.

Originally I didn't pass the url the api is mounted at on purpose to support the case where (in production) you need to proxy from one UI to many difference services and so need your development proxying behavior to match your deployment proxying behavior.

For example, if you have a UI that uses data from http://myapp.info and 'http://yourapp.ninja/api`, you'd have a production setup in something like nginx:

location /myapp  {
    proxy_pass http://myapp.info;
}

location /ninjas  {
    proxy_pass http://yourapp.ninja/api;
}

and so would generate two proxies in development mode

ember g http-proxy myapp
ember g http-proxy ninjas

In this case you want ajax('/ninjas/battles/12') to eventually request to http://yourapp.ninja/api/battles/12 not http://yourapp.ninja/api/ninjas/battles/12.

If you're developing one UI against one service and will be deploying them both under the same domain (so want the behavior of this PR), you'd just generate an http-proxy without a namespace:

ember g http-proxy

which should mount at / after asset loading attempts, yeah?