-
Notifications
You must be signed in to change notification settings - Fork 62
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
Example code does not work #7
Comments
The code in the examples folder does work. But not the code in the readme. Using the code in the readme or in the examples folder in my own folder gives me the error above. What am I missing? :( |
Found the culprit. I was using a http-proxy version that was newer than the one used by harmon. Maybe this could be mentioned in the readme. That to make require('http-proxy') work you have to |
@michaellopez thanks for the heads up. If you contribute a fix I can give you write access on this repo. |
@No9 I will see what I can do. No promises :) |
@michaellopez I think this is an example of what's required. https://github.com/nodejitsu/node-http-proxy/blob/caronte/examples/middleware/modifyResponse-middleware.js |
I'm running into the same issue. What do I need to fix it? See: http://stackoverflow.com/questions/23097898/modifying-html-response-in-node-http-proxy-using-harmon-protocol-error |
@Stwissel I'm afraid I can't be of much help. I haven't had time to wrap my head around this issue. |
Put a response into stackoverflow http://stackoverflow.com/questions/23097898/modifying-html-response-in-node-http-proxy-using-harmon-no-output-maniputlatio/23111145#23111145 Based on this https://gist.githubusercontent.com/No9/10874082/raw/38a26d15b7ecbd875eee0988c94af0333927b98a/host-multiaction.js Maybe time to do #8 |
Opened #9 as the main issue is resolved but there is a header mapping feature required |
Hi,
Was trying out your code today and I can't get the examples to work. I get the following error message:
A quick search on Google leads me to http-party/node-http-proxy#499 and http-party/node-http-proxy#510 which seem to indicate that some API change has occurred.
The text was updated successfully, but these errors were encountered: