Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
litespeed_wiki:nodejs_setup [2014/08/07 14:56]
Michael Armstrong [Add Your Node.js Files] 		litespeed_wiki:nodejs_setup [2014/12/28 21:23]
George Wang [Proxy Node.js Traffic]
Line 28: Line 28:
 ===== Proxy Node.js Traffic ===== ===== Proxy Node.js Traffic =====
  
-Now that Node.js is installed on your server, you will need to tell LSWS to send the proper traffic to your Node.js application. Starting with LSWS 4.2.13, this can be done with a just a rewrite rule (if Node.js is installed on the same server as LSWS). Simply add a rewrite rule that will redirect traffic to the port Node.js is listening on. The following is an example:+Now that Node.js is installed on your server, you will need to tell LSWS to send the proper traffic to your Node.js application. Starting with LSWS 4.2.13, this can be done with a just a rewrite rule (if Node.js is installed on the same server as LSWS). Simply add a rewrite rule that will redirect traffic to the port Node.js is listening on. The following is an example, the domain name for the site is "​example.com",​ Node.js application server is running on port 1337, add the following rewrite rule to .htaccess under document root directory. ​
  
   RewriteEngine On   RewriteEngine On
   RewriteCond %{REQUEST_FILENAME} !-f   RewriteCond %{REQUEST_FILENAME} !-f
-  ​RewriteCond %{REQUEST_FILENAME} !-d +  RewriteRule ^(.*)$ http://example.com:1337/$1 [P,L]
-  ​RewriteRule ^(.*)$ http://127.0.0.1:1337/$1 [P,L]+
  
-The above example redirects all traffic (after checking that it is a directory or file) to port 1337 (where ''​example.js''​ is running, as noted above).+The above example redirects all traffic (after checking that it is a directory or file) to port 1337 (where ''​example.js''​ is running, as noted above). ​Static files are still served by LSWS web server.  
 + 
 +If there is no need to serve static files through LSWS, you can let LSWS proxy all requests to backend application server with rewrite rule 
 + 
 +  RewriteEngine On 
 +  RewriteRule ^(.*)$ http://​example.com:​1337/​$1 [P,L]
  
 ==== If Using LSWS Below 4.2.13 or Proxying to an External Server ==== ==== If Using LSWS Below 4.2.13 or Proxying to an External Server ====
Line 51: Line 55:
 {{litespeed_wiki:​config_proxy_extapp.png?​700}} {{litespeed_wiki:​config_proxy_extapp.png?​700}}
  
-In the above configurations we have made the Location 1.2.3.4:50000. It is important that the Location match the IP (127.0.0.1 if it is on the same server) and port Node.js is running on.+In the above configurations we have made the Location 1.2.3.4:1337. It is important that the Location match the IP (127.0.0.1 if it is on the same server) and port your Node.js ​application ​is running on.
  
-After saving the configurations,​ restart LSWS to save changes. Your traffic should be redirected to Node.js now.+After saving the configurations,​ restart LSWS to save changes. Your traffic should be redirected to your Node.js ​application ​now.
  
 ===== Notes ===== ===== Notes =====
  
   * If you encounter errors using Node.js, please make sure that Node.js is started and running when using it.   * If you encounter errors using Node.js, please make sure that Node.js is started and running when using it.