Skip to content

Route target paths in Proxy Table? #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rigolepe opened this issue Apr 15, 2012 · 3 comments
Closed

Route target paths in Proxy Table? #232

rigolepe opened this issue Apr 15, 2012 · 3 comments

Comments

@rigolepe
Copy link

I've noticed there is currently no support for paths on the target host in a Proxy Table:

var options = {
  router: {
    'myhost.com/appA': '127.0.0.1:8080',
    'myhost.com/appB': '127.0.0.1:9090/appB',
    'myhost.com/appC': '127.0.0.1:9090/appC'
  }
};

The first route will work, but the second and third will hang on the '/appB' and '/appC' part behind '127.0.0.1:9090'. I sometimes have multiple apps in the same servlet container that I wish to proxy. I was able to do that in a Apache reverse proxy configuration and I hoped to be able to do the same with node.

Is any support for this planned?

@coderarity
Copy link
Contributor

Yeah, a lot of people have asked for this. I have a pull request open that would allow it, see #218

@cronopio
Copy link
Contributor

cronopio commented Jun 5, 2012

@rigolepe 0.8.1 is out, can you test it again to see if still its an issue. Thanks

@rigolepe
Copy link
Author

rigolepe commented Jun 6, 2012

Works as a charm :)

I was using CodeRarity's fix before, but now 0.8.1 does the job as well. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants