-
Notifications
You must be signed in to change notification settings - Fork 65
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
Error with connection; "Stream already opened" #20
Comments
I get the same error on every request, no matter what I do. Mac OS X 10.6.4, node 0.2.6 installed with homebrew, npm 0.2.14-6, http-console 5.1. UPDATE: newest node(0.3.5-pre) doesn't solve the issue. http-console@0.2.5, however, works on both 0.2.6 and 0.3.5 and seems to be the last version that does. |
I am getting this issue too with node version 0.2.6 and http-console version 0.5.1 Installed node and npm with brew. |
I have an Ubuntu Lucid machine tricked out with node 0.2.6 and http-console 0.5.1 and I get the same issue. curl shows my website responds fine, but trying http-console requests blow out with the Stream already opened??? Have not run into this on my other machines... some kind of evil confluence of two releases not meshing nicely? |
This stopped happening for me after an update to node 0.4 and http-console 0.6. Everything seems to work fine right now. |
@allait Thanks |
https://github.com/ry/node HEAD is 0.4 right now. I suppose it's nearly the same as 0.3.8, it's just that I'm using homebrew and it means only two options to install node.js: stable 0.2.6 or repository HEAD. |
@allait updating to node-v0.4.0-pre and http-console v0.6 works. It's fun to use. So far GET, PUT, POST and DELETE work against CouchDB |
Hi all, I just installed node 0.4 HEAD to ~/local and then npm install http-console and sure enough, it all worked fine. Thanks for the update. |
Just started with it (npm installer), but got this error (also with source version from github):
That last repeats in an endless loop..
(Using the bleeding-edge version of node: v0.3.4-pre)
Same thing happens with PUT, POST and DELETE requests
cURL'ing works:
Thoughts/ideas?
The text was updated successfully, but these errors were encountered: