node.http.Client doesn't seem to work on a Mac

[n8agrin]

Env: Mac 10.5
Example code:

var google = new node.http.Client(80, "google.com");
var req = google.get("/");
req.flush();
req.finish(function (res) {
  puts("STATUS: " + res.statusCode);
  puts("HEADERS: " + JSON.stringify(res.headers));
  res.setBodyEncoding("utf8");
  res.onBody = function (chunk) {
    puts("BODY: " + chunk);
  };
});

Running the http.Client never returns any data, just hangs and a bump in cpu usage is noted.

[ry]

I've just fixed a rather large and gaping bug in http.Client that I think was causing this. Can you please try again with HEAD?

[sixtus]

Just signed up to github - so moving my mail reply to here. And the answer is, sorry, it didn't fix the issue.

[ujh]

I can confirm that. Even at c226f81 it doesn't work on the Mac.

[ry]

okay - it's working on linux and freebsd. it will have to wait until i get mac access again.

[sixtus]

Do you have a schedule for that? I could work on a SSH account, if it'll take too long.

[ujh]

I'll setup and account for Ryan on Sunday or Monday. You're welcome to do that before that of course :)

[sixtus]

I don't think I will get our Admins to open a port before Monday. But "this weekend" is very well within my time restrictions of waiting for a working node to migrate to it.

[ry]

So - there seems to be a problem during getaddrinfo() which I can't figure out.
As a temporary solution I've made a change on macintosh which synchronously does DNS resolution for tcp clients. This is in 080fa54

Experiencing some other problems with this change on linux, so I will leave the issue open for the moment. It might be that I'm corrupting the heap at some point (but valgrind isn't telling me?).

[ry]

I'm satisfied with the hacked solution for now. Going to switch to udns at soon, so perhaps it's not even worth investigating

[ThisIsMissEm]

hmm.. using HEAD and the example code provided, I'm getting:

native runtime.js:404
throw %MakeTypeError('called_non_callable',[typeof a]);
^
TypeError: undefined is not a function
at Object.CALL_NON_FUNCTION_AS_CONSTRUCTOR (native)
at Object. (/Users/micheil/var/tmp/node-issue3.js:1:79)
at [object Object]. (node.js:897:21)
at [object Object].emitSuccess (node.js:260:13)
at [object Object]. (node.js:652:21)
at [object Object].emitSuccess (node.js:260:13)
at node.js:509:29
at node.js:950:1
at node.js:954:1

---

System Version: Mac OS X 10.6.2 (10C540)

[ry]

Miksago, the API has changed dramatically since then. Here is the example updated for v0.1.21-31-g2507b87

http = require("http");
sys = require("sys");
var google = http.createClient(80, "google.com");
var req = google.request("GET", "/");
req.flush();
req.finish(function (res) {
  sys.puts("STATUS: " + res.statusCode);
  sys.puts("HEADERS: " + JSON.stringify(res.headers));
  res.setBodyEncoding("utf8");
  res.onBody = function (chunk) {
    sys.puts("BODY: " + chunk);
  };
});

[ThisIsMissEm]

My bad for reply on a closed issue.