Morgan is used for logging request details. However, the snippet in your question doesn&#39;t make sense because it&#39;s not actually a single coherent snippet top to bottom. It is a series of examples of the various types of options you can pass to morgan. In a real program, you would only need one of them. For example:

    var express = require(&#39;express&#39;)
    var morgan  = require(&#39;morgan&#39;)
    
    var app = express()
    //This tells express to log via morgan
    //and morgan to log in the &quot;combined&quot; pre-defined format
    app.use(morgan(&#39;combined&#39;))
    //That&#39;s it. Everything in your snippet after this are just
    //other variations your might want to use

Morgan is basically a logger, on any requests being made,it generates logs automatically.

**Morgan:** is another HTTP request logger middleware for Node.js. It simplifies the process of logging requests to your application. You might think of Morgan as a helper that collects logs from your server, such as your request logs. It saves developers time because they don’t have to manually create common logs. It standardizes and automatically creates request logs.

Morgan can operate standalone, but commonly it’s used in combination with Winston. Winston is able to transport logs to an external location, or query them when analyzing a problem.

Morgan is a popular HTTP request middleware logger for Node.js and basically used as a logger. It can be used with node js&#39; winston package to consolidate HTTP request data logs with other information.

I&#39;m trying to integrate Tomcat with Apache. My aim is to redirect all the requests with
`http://localhost/myapp` to `http://localhost:8080`

I followed this guide: http://tomcat.apache.org/tomcat-8.0-doc/proxy-howto.html

My `httpd.conf` looks like this:

    Include conf.modules.d/*.conf
    LoadModule proxy_module  modules/mod_proxy.so
    
    ProxyPass         /myapp  http://localhost:8080 retry=0 timeout=5
    ProxyPassReverse  /myapp  http://localhost:8080

My server.xml in apache-tomcat looks like this:

    &lt;Connector port=&quot;8080&quot; protocol=&quot;HTTP/1.1&quot; connectionTimeout=&quot;20000&quot; redirectPort=&quot;8443&quot; proxyPort=&quot;80&quot; /&gt;

Now when I try the url `http://localhost/myapp`, it gives `503 Service Unavailable` error.

Both Tomcat and Apache are up and running. The URL `http://localhost:8080` works fine. 

Can there be an issue with file permissions?

For `tomcat` the user and group are `root/root` and for `httpd`, the user and group are `apache/apache`

Am I missing something or am I doing it wrong?

Httpd version is 2.4.6 and Tomcat&#39;s version is 8.0


The httpd error logs:

    [proxy:error] [pid 19905] (13)Permission denied: AH00957: HTTP: attempt to connect to 127.0.0.1:8080 (localhost) failed
    
    [proxy:error] [pid 19905] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 0s
    
    [proxy_http:error] [pid 19905] [client ::1:51615] AH01114: HTTP: failed to make connection to backend: localhost

**Solved!**

The answer is here: http://sysadminsjourney.com/content/2010/02/01/apache-modproxy-error-13permission-denied-error-rhel/

Httpd returning 503 Service Unavailable with mod_proxy for Tomcat 8

I have a simple NSURLRequest:

    [NSURLConnection sendAsynchronousRequest:myRequest queue:queue completionHandler:^(NSURLResponse *response, NSData *data, NSError *error) {
        // do stuff with response if status is 200
    }];

How do I get the status code to make sure the request was ok?

NSURLResponse - How to get status code?

In an express tutorial, the author was using the `npm module morgan`. What can morgan do for an express app? Could anyone help me understand this?

Got this by googling, but I do not understand anything here:

    var express = require(&#39;express&#39;)
    var morgan  = require(&#39;morgan&#39;)
    
    var app = express()
    app.use(morgan(&#39;combined&#39;))
    morgan(&#39;combined&#39;)
    
    morgan(&#39;:remote-addr :method :url&#39;)
    
    morgan(function (tokens, req, res) {
      return req.method + &#39; &#39; + req.url
    })



What does `morgan` module have to do with express apps?

In an express tutorial, the author was using the <code>npm module morgan</code>. What can morgan do for an express app? Could anyone help me understand this?
Got this by googling, but I do not understand anything here:
<pre><code class="hljs language-javascript">var express = require('express')
var morgan = require('morgan')

var app = express()
app.use(morgan('combined'))
morgan('combined')

morgan(':remote-addr :method :url')

morgan(function (tokens, req, res) {
 return req.method + ' ' + req.url
})
</code></pre>

In my node app, I am using express. all works fine, But i am getting error in the `cmd`. I use all are updated modules...

**my code :**

    var express = require(&#39;express&#39;);
    var bodyParser = require(&#39;body-parser&#39;);
    var jade = require(&#39;jade&#39;);
    var app = express();
    app.set(&#39;view engine&#39;, &#39;jade&#39;);
    app.set(&#39;views&#39;, __dirname + &#39;/views&#39;);
    app.use(express.static(__dirname + &#39;/public&#39;));
    
    
    app.use(bodyParser.json()); // to support JSON-encoded bodies
    app.use(bodyParser.urlencoded()); // to support URL-encoded bodies
    
    
    app.get(&#39;/&#39;,function(req,res){
    	res.render(&#39;index.jade&#39;);
    });
    
    app.get(&#39;/login&#39;,function(req,res){
    	res.render(&#39;index.jade&#39;);
    });
    
    app.post(&#39;/login&#39;,function(req,res){
    	console.log(req.body);
    });
    
    app.get(&#39;/signup&#39;,function(req,res){
    	res.render(&#39;signup.jade&#39;);
    });
    
    var env = process.env.PORT || 3000;
    
    
    app.listen(env, function(req, res){
    	console.log(&#39;i am working!&#39;);
    });



**Error:**

    D:\myLogin&gt;node app
    body-parser deprecated undefined extended: provide extended option app.js:11:20 //why i am getting this?
    i am working!
    { username: &#39;jbarif@gmail.com&#39;, password: &#39;pass&#39; } // i am getting response


Can any help me to understand this issue please?

express throws error as `body-parser deprecated undefined extended`

I have a huge collection of documents in my DB and I&#39;m wondering how can I run through all the documents and update them, each document with a different value.

How can I use a cursor.forEach() in MongoDB using Node.js?

How can I share a session with Socket.io 1.0 and Express 4.x? I use a Redis Store, but I believe it should not matter. I know I have to use a middleware to look at cookies and fetch session, but don&#39;t know how. I searched but could not find any working 

		var RedisStore = connectRedis(expressSession);
		var session = expressSession({
			store: new RedisStore({
				client: redisClient
			}),
			secret: mysecret,
			saveUninitialized: true,
			resave: true
		});
		app.use(session);

		io.use(function(socket, next) {
			var handshake = socket.handshake;
			if (handshake.headers.cookie) {
				var str = handshake.headers.cookie;
				next();
			} else {
				next(new Error(&#39;Missing Cookies&#39;));
			}
		});


How to share sessions with Socket.IO 1.x and Express 4.x?

What is the benefit of using `console.log` vs `console.info`?
Or any of the other console commands for that matter? 

    console.info(&quot;info&quot;);
    console.error(&quot;error&quot;);
    console.warn(&quot;warn&quot;);

vs

    console.log(&quot;log&quot;);

I thought it might change the color of the output or concatenate some sort of label, but they seem to all do the same thing. And according to the documentation here:

https://nodejs.org/api/console.html#console_console_info_data

they seem to all do the same as `console.log`


Node.js console.log vs console.info

I am trying to connect to MSSQL 2012 using NodeJS with the [mssql](https://patriksimek.github.io/node-mssql/) connection interface. 

When attempting to connect I get the following error:

    { [ConnectionError: Failed to connect to localhost:1433 - connect ECONNREFUSED]
      name: &#39;ConnectionError&#39;,
      message: &#39;Failed to conncet to localhost:1433 - connect ECONNREFUSED&#39;,
      code: &#39;ESOCKET&#39; }

Any ideas on how to fix this?

Node.js MSSQL tedius ConnectionError: Failed to connect to localhost:1433 - connect ECONNREFUSED

I have a route.js which looks like this:

    module.exports = function(app) {

      app.get(&#39;/tip&#39;, function(req, res) {
        res.render(&quot;tip&quot;);
      });

      app.get(&#39;/article&#39;, function(req, res) {
       res.render(&quot;article&quot;);
      });

      app.get(&#39;/article1&#39;, function(req, res) {
       res.render(&quot;article1&quot;);
      });

      app.get(&#39;/article2&#39;, function(req, res) {
       res.render(&quot;article2&quot;);
      });

      app.get(&#39;/article3&#39;, function(req, res) {
       res.render(&quot;article3&quot;);
      });

      app.get(&#39;/modules/:name&#39;, function(req, res) {
        var name = req.params.name;
        res.render(&#39;modules/&#39; + name);
      });

      app.get(&#39;/modules/esaver/:name&#39;, function(req, res) {
        var name = req.params.name;
        res.render(&#39;modules/esaver/&#39; + name);
      });

    };

Considering i have over 200 different routes to create, i would end up with stuff like &#39;article1&#39;, &#39;article2&#39; etc

and my app.js is like:

    var express = require(&#39;express&#39;)
      ,http = require(&#39;http&#39;)
      ,fs = require(&#39;fs&#39;)
      ,path = require(&#39;path&#39;);

    var app = express();

    html_templates = __dirname + &#39;/html_templates&#39;;

    app.set(&#39;views&#39;, html_templates + &#39;/views&#39;);
    app.set(&#39;view engine&#39;, &#39;jade&#39;);

    app.use(&#39;/Core&#39;, express.static(__dirname + &#39;/Core&#39;));


    app.listen(3000, function () {
     console.log(&quot;express has started on port 3000&quot;);
    });

    require(&#39;./html_templates/controller/routes.js&#39;)(app);

Is there any dynamic way to create this?

How to configure dynamic routes with express.js

I am playing around with Nodejs and express by building a small rest API. My question is, what is the good practice/best way to set the code status, as well as the response data?

Let me explain with a little bit of code (I will not put the node and express code necessary to start the server, just the router methods that are concerned):

    router.get(&#39;/users/:id&#39;, function(req, res, next) {
      var user = users.getUserById(req.params.id);
      res.json(user);
    });


    exports.getUserById = function(id) {
      for (var i = 0; i &lt; users.length; i++) {
        if (users[i].id == id) return users[i];
      }
    };

The code below works perfectly, and when sending a request with Postman, I get the following result:
![enter image description here][1]

As you can see, the status shows 200, which is OK. But is this the best way to do this? Is there a case where I should have to set the status myself, as well as the returned JSON? Or is that always handled by express?

For example, I just made a quick test and slightly modified the get method above:

    router.get(&#39;/users/:id&#39;, function(req, res, next) {
      var user = users.getUserById(req.params.id);
      if (user == null || user == &#39;undefined&#39;) {
        res.status(404);
      }
      res.json(user);
    });

As you can see, if the user is not found in the array, I will just set a status of 404.

Resources/advices to learn more about this topic are more than welcome.


  [1]: http://i.stack.imgur.com/0EMs8.png

Proper way to set response status and JSON content in a REST API made with nodejs and express

while trying this mongo command in ubuntu
I am getting this error.

        ritzysystem@ritzysystem-Satellite-L55-A:~$ mongo
        MongoDB shell version: 2.6.1
        connecting to: test
        2014-10-06T12:59:35.802+0530 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
        2014-10-06T12:59:35.802+0530 Error: couldn&#39;t connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146
        exception: connect failed


how can I rectify this is anyone had the same problem.

Content Type	Original Author	Original Content on Stackoverflow
Question	3gwebtrain	View Question on Stackoverflow
Solution 1 - node.js	Peter Lyons	View Answer on Stackoverflow
Solution 2 - node.js	Krishna Ganeriwal	View Answer on Stackoverflow
Solution 3 - node.js	Elle Kiumarsian	View Answer on Stackoverflow
Solution 4 - node.js	Ravi Malviya	View Answer on Stackoverflow

What does `morgan` module have to do with express apps?

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Solution 2 - node.js

Solution 3 - node.js

Solution 4 - node.js

NSURLResponse - How to get status code?

Httpd returning 503 Service Unavailable with mod_proxy for Tomcat 8

Attributions