《nginx》专题

All nginx security issues should be reported to security-alert@nginx.org. Patches are signed using one of the PGP public keys. Vulnerabilities with Windows directory aliases Severity: medium CVE-2011-

Read-only Subversion repositories: code: svn://svn.nginx.org/nginx site: svn://svn.nginx.org/nginx.org Trac source browser Pre-Built Linux Packages for Stable To enable automatic updates of Linux pack

nginx can be controlled with signals. The process ID of the master process is written to the file /usr/local/nginx/logs/nginx.pid by default. This name may be changed at configuration time, or in ngin

Name-based virtual servers nginx first decides which server should process the request. Let’s start with a simple configuration where all three virtual servers listen on port *:80: server { liste

Installing nginx How nginx processes a request Server names Connection processing methods nginx for Windows Controlling nginx Configuring HTTPS servers Configuration file measurement units Setting Up

Support read data from Tengine/Nginx by common socket or unix domain socket. Source file Get source file (https://github.com/taobao/tsar-mod_nginx) Quick start Install tsar. Generate a new module by u

Background We've implemented the support of SO_REUSEPORT [1] in Tengine. To see the performance improvement, we did a very simple benchmark with four Linux boxes. Three boxes were employed as clients,

nginx can be controlled with signals. The process ID of the master process is written to the file /usr/local/nginx/logs/nginx.pid by default. This name may be changed at configuration time, or in ngin

基于名字的虚拟主机 Nginx首先选定由哪一个虚拟主机来处理请求。让我们从一个简单的配置（其中全部3个虚拟主机都在端口*：80上监听）开始： server { listen 80; server_name example.org www.example.org; ... } server { listen 80; server_nam

安装nginx Nginx如何处理一个请求 虚拟主机名 连接处理方法 nginx Windows版使用说明 Controlling nginx 配置HTTPS服务器 配置文件中的计量单位 设置哈希表 调试日志 How-To 转换rewrite规则 如何在Win32平台上用Visual C编译nginx Setting up development environment with nginx on

All nginx security issues should be reported to security-alert@nginx.org. Patches are signed using one of the PGP public keys. Vulnerabilities with Windows directory aliases Severity: medium CVE-2011-

Read-only Subversion repositories: code: svn://svn.nginx.org/nginx Read-only Mercurial repositories: site: http://hg.nginx.org/nginx.org Trac source browser Pre-Built Linux Packages for Stable To enab

背景 我们在Tengine中实现了SO_REUSEPORT [1]的支持。为了查看其效果，我们进行了一个简单的测试。我们在同一个局域网中部署了一共四台同等配置的服务器，其中一台同时部署Tengine和Nginx，分别监听不同的端口，另外三台部署ab，三个ab同时压测，从总并发100逐步递增到1000，分别压测Tengine和Nginx，访问空gif图片。 三种压测场景： Tengine打开SO_R

nginx [engine x]是Igor Sysoev编写的一个HTTP和反向代理服务器，另外它也可以作为邮件代理服务器。 它已经在众多流量很大的俄罗斯网站上使用了很长时间，这些网站包括Yandex、Mail.Ru、VKontakte，以及Rambler。据Netcraft统计，在2012年8月份，世界上最繁忙的网站中有11.48%使用Nginx作为其服务器或者代理服务器。部分成功案例请见： N

我们在部署之后, 会发现Vuejs会遇到js 的经典问题: 远程服务器地址不对,或者跨域问题. 前提: 我们的真正后台接口是: http://siwei.me/interface/blogs/all 如下: 域名404 问题 这个问题看起来如下: 这个问题是由于源代码中,访问 /interface/blogs/all 这个接口引起的: this.$http.get('/api/interface/