nodejs httprequest with data - getting error getaddrinfo ENOENT

Question

Update - Answered by self

I see one has to make sure that the DNS is resolved properly from the machine, check out the node documentation to make sure that domain is resolvable.

Original Question

i am writing a nodes based program,in which the user can ask me to do a httprequest on their behalf {off course they provide me with some data, and method to call with} but every time i do a httprequest it gives me an error

getaddrinfo ENOENT this is how my code looks

function makehttprequest(deviceid, httpaction, httppath,methods, actiondata, callback) { console.log('we are here with httpaction' + httpaction + ' path ' + httppath + ' method ' + methods + ' action data ' + actiondata);  //do the http post work, get the data, and call the callback function with return data  var options = {    host: httpaction,    port: 80,    path: httppath,    method: methods  };      try {       var req = http.request(options, function(res) {         console.log('STATUS: ' + res.statusCode);         console.log('HEADERS: ' + JSON.stringify(res.headers));         res.setEncoding('utf8');         res.on('data', function (chunk) {           console.log('BODY: ' + chunk);         });       });     } catch(e) {       console.log('error as : ' + e.message);     }      req.on('error', function(e) {       console.log('problem with request: ' + e.message);     });      // write data to request body     console.log('writing data to request ..');     req.write(actiondata);     console.log('finished writing data to request…');     req.end();     console.log('request ended…'); } 

Answer 1

I've seen this happen when your host (which you pass in as httpaction) has the scheme (so "http://") in front of it. Your host should strictly be the domain like "www.google.com" not "http://www.google.com" or "www.google.com/hello-world" or "http://www.google.com/hello-world".

Keep it just the domain.

Here's an example: http://allampersandall.blogspot.com/2012/03/nodejs-http-request-example.html

Answer 2

The problem can also happen if you have a trailing slash:

Good: "www.google.com"

Bad: "www.google.com/"