[轉]How to Mirror Your Traffic with Nginx
https://www.serverlab.ca/tutorials/linux/web-servers-linux/how-to-mirror-your-traffic-with-nginx/
https://www.serverlab.ca/tutorials/linux/web-servers-linux/how-to-mirror-your-traffic-with-nginx/
https://www.tecmint.com/nginx-web-server-security-hardening-and-performance-tips/?fbclid=IwAR3WRK-N-buun8QIMDUbzes72-w6p8SKCxnzr0sGU_PFAyudPRbHiumtFu0
https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/nginx-ingress-controllers.md F…………………………. ================ https://mritd.me/2017/03/04/how-to-use-nginx-ingress/
https://zhuanlan.zhihu.com/p/41354937
.https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/ http://www.queryadmin.com/1654/tuning-linux-kernel-tcp-parameters-sysctl/ https://blogs.dropbox.com/tech/2017/09/optimizing-web-servers-for-high-throughput-and-low-latency/ Don’t USE net.ipv4.tcp_tw_recycle=1 —don’t use it—it was already broken for users behind NAT, but if you upgrade your kernel, it will be broken for everyone. net.ipv4.tcp_timestamps=0 —don’t disable them unless you know all side-effects and you are OK with them. For example, one of non-obvious side effects is that you will loose window scaling and SACK options on syncookies. https://read01.com/zh-tw/KBgmj7.html Don’t USE net.ipv4.tcp_tw_recycle=1 net.ipv4.tcp_tw_reuse=1 /*Only you know, sometime can do*/ ...