使用nginx处理静态资源请求，其余交给node

Posted 2020-10-14 三十亿少女的梦

 　　由于项目后台使用的是node，然而node不适合对静态资源的处理，因为他的异步处理（事件轮询）机制，所以更擅长的是密集I/O型的应用，所以我就有了一个想法，使用nginx来做反向代理，当请求的是静态资源的时候，直接由nginx（监听80端口）自己处理并返回，其他非静态资源请求转发至node(8080端口)，由node来处理。下面是我的nginx配置文档，nginx安装请自行百度，大把资料啦~

 

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  ‘$remote_addr - $remote_user [$time_local] "$request" ‘
    #                  ‘$status $body_bytes_sent "$http_referer" ‘
    #                  ‘"$http_user_agent" "$http_x_forwarded_for"‘;

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    server {
        listen       80;
        server_name  www.guangzhouyueyang.com;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;
        location ~ .*\.(gif|jpg|jpeg|png|bmp|swf)$     
        {
         root html;
         expires 30d;
        }
        location ~ .*\.(css)?$
        {
         root html;
         expires 1h;
        }
        location ~ .*\.(js)?$
        {
         root html;
         expires 1h;
        }

        location / {
           proxy_set_header X-Real-IP $remote_addr;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header Host $http_host;
           #proxy_set_header X-Nginx-Proxy true;
           proxy_set_header Connection "";
           proxy_pass http://localhost:8080;
        }

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }

        # proxy the php scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
        #    proxy_pass   http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        #location ~ \.php$ {
        #    root           html;
        #    fastcgi_pass   127.0.0.1:9000;
        #    fastcgi_index  index.php;
        #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
        #    include        fastcgi_params;
        #}

        # deny access to .htaccess files, if Apache‘s document root
        # concurs with nginx‘s one
        #
        #location ~ /\.ht {
        #    deny  all;
        #}
    }


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}


    # HTTPS server
    #
    #server {
    #    listen       443 ssl;
    #    server_name  localhost;

    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_cache    shared:SSL:1m;
    #    ssl_session_timeout  5m;

    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers  on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

 

　　配置解释：当请求是以（css, js, gif, jpg, jpeg, png, bmp, swf)结尾的时候则nginx直接拦截请求（上面源码中标红的部分），由nginx静态服务器直接返回静态资源，而如果不是的话则将请求转发到node服务（上面源码中标蓝的部分），由node来完成其余请求。