Mittwoch, 18. Mai, 2016

Finishing Angular TODO application and deploying to production 149
• Serving static files like images, CSS, js, and HTML. Node may be less efficient compared to
using a proper static file web server (Node may also be faster in select scenarios, but this is
unlikely to be the norm). On top of files serving more efficiently, you won’t have to worry
about handling eTags or cache control headers the way you would if you were servings things
out of Node. Some frameworks may handle this for you, but you would want to be sure.
Regardless, still probably slower.
• More easily display meaningful error pages or fall back onto a static site if your node service
crashes. Otherwise users may just get a timed out connection.
• Running another web server in front of Node may help to mitigate security flaws and DoS
attacks against Node. For a real-world example, CVE-2013-4450²²⁴ is prevented by running
something like Nginx in front of Node²²⁵.
So, with being convinced that having NGINX in front of Node.js application is a good thing,
following are the steps on how to install and configure it. First, update the apt-get package lists
with the following command:
1 sudo apt-get update
Then install NGINX using apt-get:
1 sudo apt-get install nginx
Now open the default server block configuration file for editing:
1 sudo vi /etc/nginx/sites-available/default
and add this to it:
1 server {
2 listen 80;
3
4 server_name meantodo.com;
5
6 location / {
7 proxy_pass http://127.0.0.1:1337;
8 proxy_http_version 1.1;
9 proxy_set_header Upgrade $http_upgrade;
10 proxy_set_header Connection 'upgrade';
11 proxy_set_header Host $host;
12 proxy_cache_bypass $http_upgrade;
13 }
14 }
²²⁴http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-4450
²²⁵http://blog.nodejs.org/2013/10/22/cve-2013-4450-http-server-pipeline-flood-dos/