-
Notifications
You must be signed in to change notification settings - Fork 2k
proxyWebSocketRequest not utilizing routes #72
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
Comments
I'll have someone look into this, looks like it could be a bug. You should understand that the routing table stuff is all for convenience. If you read the "rather depressing documentation" you'll understand that building a custom routing scenario is trivial. |
This is easy enough to fix. For optimization purposes (i.e. less function invocations on each request), this code (https://github.com/nodejitsu/node-http-proxy/blob/master/lib/node-http-proxy.js#L344-372) should basically just be duplicated inside of @dominctarr thoughts? Have you had a chance to really dig through the code base yet? |
The gist does not have enough code to reproduce the problem, and the websocket examples are broken, but looks fairly simple, will reproduce first. the websocket examples are broken, then fix. |
fixed in efa17ef duplicating the code is a problem, will refactor when I'm more familiar with the code base. |
While exploring node-http-proxy, among other things (such as the rather depressing documentation), I noticed that this function doesn't utilize routing preferences set when calling HttpProxy(options).
https://gist.github.com/1088665
The text was updated successfully, but these errors were encountered: