IIS extension iisnode installation and configuration notes for running Node.js_node.js

At the beginning of this year, I planned to use Node.js to rewrite the blog program based on the Express framework and say goodbye to ASP.NET. However, the VPS I am currently using is a Windows Server system and an IIS server. If both Express and IIS are allowed to listen to port 80, there will obviously be a conflict. Fortunately, there is an extension called iisnode that can host Node.js programs on IIS. Moreover, such hosting also means that you can use various functions in IIS (process management, GZip compression, logs, cache, permission control, domain name binding, etc.).

To use iisnode, you must install:

1.Node.js
2.URL Rewrite module of IIS
3.iisnode

After installation, follow the usual operations and create a site in the IIS manager, pointing to the directory of the Express program. The key is to add a web.config file:

Copy code The code is as follows:

                                                                                                       
        
 

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 
                                                                                                                                                                                                                                                                                                     in                                                                                                                                               
                                                                                           

This content can also be configured through the visual interface of IIS Manager. It probably means rewriting all requests to bin/www, and using the iisnode extension to run bin/www. However, after opening the site, this error message appeared:

Copy code

The code is as follows: The request filtering module is configured to reject paths in URLs that contain a hiddenSegment section At first I thought it was unclear, but then I suddenly realized that the bin directory in ASP.NET is a special directory that is not allowed to be accessed. Rewrite the request to bin/www, which happens to hit this rule. So, just change the directory name, for example, change bin to launch (it turns out that this is not a good practice, I will talk about it later), and web.config should also be adjusted accordingly:

Copy code

The code is as follows:

                                                                                                     
        
 

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 
                                     
                                                                                                                                             
                                                                                           

Restart the site in IIS manager and access it again. It finally runs. It’s not easy! But it was still too early to be happy.

During the process of testing the function of the program, I found that the IP obtained was empty. In the Express framework, IP is obtained through req.ip, which in turn obtains the value from REMOTE_ADDR in the request header. Through a simple test code, it was found that the value of REMOTE_ADDR is also empty. Obviously, this header information was lost in the process from IIS to Node.js. After some Google, I found that iisnode does have

this problem. The official solution is to use X-Forword-For, but I found another way.

There is a configuration in Web.config (added before ) that can retain REMOTE_ADDR:

Copy code

The code is as follows:

According to the instructions, the reserved REMOTE_ADDR will be renamed x-iisnode-REMOTE_ADDR, so you have to overwrite the value of req.ip once and add a middleware function in Express app.js:

Copy code

The code is as follows: app.use(function(req, res, next) { req.ip = req.headers['x-iisnode-REMOTE_ADDR']; next();

});

However, after such adjustment, the obtained IP is still empty, which makes people wonder whether the assignment of req.ip failed. Looking at the source code of Express, we can find that req.ip is defined by define getter, so to overwrite it, you have to define it again:

Copy code

The code is as follows: app.use(function(req, res, next) { Object.defineProperty(req, 'ip', {           get: function() { return this.headers['x-iisnode-REMOTE_ADDR']; }

});

next();
});



This problem is finally solved, but this is not a good method. It will be troublesome if Express sets req.ip to read-only in the future.

Continuing testing, another problem was discovered. Normally, the file upload function in the blog background will transfer files to the public/upload directory, but in fact, the public/upload folder is generated in the launch directory (the original bin directory). In fact, the reason is that the www file as the program entry is in the launch directory, so the launch directory becomes the execution directory of the application. My solution is to change the name of the launch directory back to bin, and create a launch.js in the root directory to call bin/www:

Copy code

The code is as follows: #!/usr/bin/env node require('./bin/www');

然后把程序入口改为launch.js：

复制代码 代码如下:

   
       
           
       

       
           
               
                   
                   
               
           
       

       
   

显然，iisnode还不是一个成熟的产品，当然Node.js也不是（至今还没1.0），一切都有待进一步探索和完善。