国产av日韩一区二区三区精品,成人性爱视频在线观看,国产,欧美,日韩,一区,www.成色av久久成人,2222eeee成人天堂

My website is across computer rooms, one nginx is used as a reverse proxy, and the real web server is in another computer room

The nginx configuration for reverse proxy is roughly as follows:

upstream real.sites {
    server 123.123.123.123;

    // 用keepalive保存長(zhǎng)連接，降低頻繁創(chuàng)建連接的開銷
    keepalive 16;
}

proxy_cache_path /path/to/cache levels=1:2 keys_zone=static_cache:100m;

server {
    server_name     www.example.com;

    // 把真正的IP地址放到header的X-Forwarded-For里面
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_http_version 1.1;
    proxy_set_header Connection "";

    proxy_next_upstream http_503;

    // 把靜態(tài)資源緩存起來(lái)，減少服務(wù)器間數(shù)據(jù)傳輸
    location ~ \.(css|js|jpg|png|gif|ico)$ {
        proxy_cache static_cache;
        proxy_pass http://real.sites;
    }

    location / {
        proxy_pass http://real.sites;
    }
}

This deployment method is greatly affected by the quality of the network in the computer room. If the network in the computer room is strong, it will be fine. nginx itself has not caused any trouble.

In fact, varnish should be more suitable for this than nginx. However, I am not familiar with varnish, so I just use nginx.

Properly.