Can't proxy to pow's domains about em-proxy HOT 3 CLOSED

Indeed, that's exactly what it does (resolve the name when you start it). Not familiar enough with pow to know the behavior you want... or if it even makes sense in the context of em-proxy.

from em-proxy.

I have a couple rack apps setup locally with pow and am on my way to build an API proxy. Say there are app1.foo.dev, app2.foo.dev and apis.foo.dev. I would want apis.foo.dev/app1 to route requests to app1 and so on for app2. Is it a good use case for em-proxy?

In production, I can totally see this approach works since em-proxy will bind to app's IP and each app will have its own IP on an individual machine. But in development with pow, I met the problem as I mentioned.

Thanks,
Owen

from em-proxy.

Before any TCP connection can be made, we resolve the hostname to the IP address. When the request is routed, it'll connect to 127.0.0.1. If pow is smart enough to look at the headers and your routing paths and then do the right thing.. then it will work.

em-proxy is an IP proxy, it doesn't understand anything about HTTP or any other protocols. In theory, you can make it be aware of higher protocols, but that will require custom code.

from em-proxy.