Nginx深入解析与模块开发指南

DOC文件

5星 · 超过95%的资源 | 下载需积分: 0 | 226KB | 更新于2024-07-25 | 173 浏览量 | 举报收藏

立即下载

"该文档是关于Nginx的详细教程，涵盖了从安装配置到源码分析，再到模块编写，以及编译器参数和系统函数的使用。适合Nginx初学者，旨在帮助读者巩固和提升Nginx相关技能，弥补知识不足。" 本文档主要分为五个章节： **Chapter 1 前言** 章节介绍了互联网编程中HTTP服务器的重要性，特别是C语言实现的服务器如Apache、Lighttpd和Nginx。Nginx因其速度、低资源占用和出色的proxy及rewrite功能而受到青睐，广泛用于大型网站的前端服务。然而，Nginx的文档和用户经验相对匮乏，使得技术交流困难。 **Chapter 2 基本配置** 这一章详细讲解了Nginx的安装过程，包括配置说明和启动与控制的方法。安装部分涵盖了从下载到编译安装的步骤，配置说明则涉及配置文件的结构和常用指令，启动和控制部分介绍如何管理Nginx服务，如启动、停止、重载配置等。 **Chapter 3 深入源码** 本章深入解析了Nginx的源码结构，包括`configure`配置脚本的使用，Nginx源码编写的一般习惯，以及常用的底层库。核心模块如`core`、`event`和`http`的结构和功能也进行了详细阐述，帮助读者理解Nginx的工作原理。 **Chapter 4 模块编写** 这一章节重点在于如何编写Nginx的模块，尤其是HTTP模块。对于想要自定义Nginx功能的开发者，这部分提供了关键的指导，包括如何构建基于Nginx的高性能服务器，并详细讲解了HTTP模块的编写方法。 **Chapter 5 附录** 附录包含了编译器参数和系统函数的相关信息，为读者提供进一步的技术参考，以便在实际操作中优化Nginx的编译和利用系统函数进行高效开发。通过这份详尽的文档，初学者可以系统地学习Nginx，从基础的部署配置到高级的源码分析和模块开发，全面掌握Nginx的使用和定制。同时，对于已经有一定经验的开发者，也可以从中找到解决特定问题的线索和方法，提升对Nginx的理解和应用水平。

must use a combination of rewrite and root.

client_body_in_file_only

语法: client_body_in_file_only on|off

缺省值: client_body_in_file_only off context: http, server, lo-cation The directive enables to store a client request

body in a file. Please note that the file at the request completion will not be removed if the directive is enabled.

The directive can be used for debugging and for the $r->request_body_file method in the ngx_http_perl_module

module.

client_body_buffer_size

语法: client_body_buffer_size the_size

缺省值: client_body_buffer_size 8k/16k context: http, server, location The directive specifies the client request

body buffer size. If the request body is more than the buffer, then the entire request

body or some part is written in a temporary file.The 缺省值 size is equal to two pages size, depending on platform

it is either 8K or 16K.

client_body_temp_path

语法: client_body_temp_path dir-path [ level1 [ level2 [ level3 ] ]]

缺省值 : client_body_temp_path client_body_temp context: http, server, location The directive assigns the

directory for storing the temporary files in it with the body of the request. In the dir-path a hierarchy of

subdirectories up to three levels are possible. For example

1 client_body_temp_path /spool/nginx/client_temp 1 2;

The directory structure will be like this: /spool/nginx/client_temp/ 7/45/00000123457

client_body_timeout

语法: client_body_timeout time

缺省值: client_body_timeout 60 context: http, server, location Directive sets the read timeout for the request body

from client. The timeout is set only if a body is not get in one readstep. If after this time the client send nothing,

nginx returns error “Request time out” (408).

client_header_buffer_size

语法: client_header_buffer_size size

缺省值: client_header_buffer_size 1k context: http, server Direc-tive sets the headerbuffer size for the request

header from client. For the overwhelming majority of requests it is completely sufficient a buffer size of 1K.

However if a big cookie is in the request-header or the request has come from a wap-client the header can not be

placed in 1K, therefore, the request-header or a line of request-header is not located completely in this buffer

nginx allocate a bigger buffer, the size of the bigger buffer can be set with the instruction

large_client_header_buffers.

client_header_timeout

语法: client_header_timeout time

缺省值: client_header_timeout 60 context: http, server Directive assigns timeout with reading of the title of the

request of client. The timeout is set only if a header is not get in one readstep. If after this time the client send

nothing, nginx returns error “Request time out” (408).

client_max_body_size

语法: client_max_body_size size

缺省值: client_max_body_size 1m context: http, server, location Directive assigns the maximum accepted body

size of client request,

indicated by the line “Content-Length” in the header of request. If size is greater the given one, then the client

gets the error “Request Entity Too Large” (413). It is necessary to keep in mind that the browsers do not know

how to correctly show this error.

缺省值_type

语法:缺省值_type MIME-type

缺省值:缺省值_type text/plain context: http, server, location default_type assigns the default MIME-type to be

used for files where the standard MIME map doesn’t specify anything. See also types Example:

1 location = / proxy . pac {

2 default_type application /x.ns.proxy.autoconfig ;

3 }

4 location = / wpad . dat {

5 rewrite . / proxy . pac ;

6 default_type application /x.ns.proxy.autoconfig ;

7 }

error_page

语法: error_page code [ code... ] [ = |=answer-code ] uri

缺省值: no context: http, server, location, if in location The directive specifies the URI, which will be showed for

the errors indicated. Example of the use:

1 error_page 404 /404.html;

2 error_page 502 503 504 /50x.html;

3 error_page 403 http://example.com/forbidden.html;

Furthermore, it is possible to change the code of answer to another, for example: error_page 404 =200 /.empty.gif;

If an erroneous answer is processed by the proxied or FastCGI server and this server can return the different

answer codes, for example, 200, 302, 401 or 404, then it is possible to issue the code returned: error_page 404 = /

404.php;

index

语法: index file [file...]

缺省值: index index.html context: http, server, location Directive determines the file(s) which will be used as the

index. It’s possible to use variables in the name of file. The presence of the files is checked in the order of their

enumeration. A file with an absolute path can be put at the end. Example using a variable: index index. $geo.html

index.0.html /index.html;

internal

语法: internal

缺省值 : no context: location internal indicates that the match-ing location can be used only for so called

“internal” requests. For

external requests it will return the error “Not found” (404). Inter-nal requests are the following: requests

redirected by the instruc-tion error_page subrequests created by the command include virtual of the

“ngx_http_ssi_module” module requests changed by the instruction rewrite of the “ngx_http_rewrite_module”

module An example to prevent clients fetching error pages directly:

1 error_page 404 /404.html; 2 location /404.html {

internal; 4}

keepalive_timeout

语法: keepalive_timeout time [ time ]

缺省值 : keepalive_timeout 75 context: http, server, location Directive assigns the timeout, for keep-alive

connections with the client. The second parameter assigns value in the line “Keep-Alive: timeout=time” in the

header of answer. The parameters can differ from each other. Line “Keep-Alive: timeout=time” understands

Mozilla and Konqueror. MSIE itself shuts keep-alive connection approximately after 60 seconds.

large_client_header_buffers

语法: large_client_header_buffers number size

缺省值: large_client_header_buffers 4 4k/8k context: http, server Directive assigns the maximum number and size

of buffers for large headers to read from client request. The request line can not be bigger then the size of one

buffer, if the client send a bigger header nginx returns error “Request URI too large” (414). The longest header

line of request also must be not more than the size of one buffer, otherwise the client get the error “Bad request”

(400). Buffers are separated only as needed. By default the size of one buffer is equal to the size of page,

depending on platform this either 4K or 8K, if at the end of working request connection converts to state keep-

alive, then these buffers are freed.

limit_except

语法: limit_except methods {…}

缺省值: no context: location Directive limits HTTP-methods, acces-sible inside location. For the limitation can be

used the directives of modules ngx_http_access_module and ngx_http_auth_basic_module: limit_except GET

{ allow 192.168.1.0/32; deny all; }

limit_rate

语法: limit_rate speed

缺省值: no context: http, server, location, if in location Direc-tive assigns the speed of transmission of the answer

to client. Speed is assigned in the bytes per second. Limitation works only for one connection, i.e., if client opens

2 connections, then total velocity

will be 2 times than higher limited. If it is necessary to limit speed for the part of the clients at the level of server,

then directive limit_rate for this does not be suitable. Instead of this should be assigned the necessary speed of

variable $limit_rate:

1 2 3 4 server if } { ( $slow ) { set $limit_rate 4k;

6 …

7 8 }

listen

]

缺省值 : listen 80 context: server The directive specifies the address and port, on which the server accepts

requests. It is possible to specify address or port only, besides, an address can be the server name, for example:

1 listen 127.0.0.1:8000;

2 listen 127.0.0.1;

3 listen 8000;

4 listen *:8000;

5 listen localhost :8000;

If only address is given, then 缺省值 port 80 is used. If the directive has the”缺省值” parameter, then the server,

剩余45页未读，继续阅读

niaowxf

粉丝: 11

Nginx深入解析与模块开发指南

计算机后端-PHP视频教程. Nginx-01Nginx实战.doc

Nginx讲义.doc

nginx教程.doc

Nginx服务.doc

nginx安装.doc

linux下Nginx配置.doc

Linux下详细安装部署Nginx教程.doc

k8s 新版本 部署 Ingress-nginx controller.doc

Linux + Nginx 0.8.x + PHP 5.2.14（FastCGI）+ Mysql.doc

Nginx0.7.x+PHP5.2.10（FastCGI）搭建胜过Apache十倍的Web服务器.doc

Window+Nginx.doc

FastDFS+Nginx.doc

nginx+keepalived使用文档.doc

nginx常用命令.doc

nginx编译参数.doc

nginx使用教程.doc

nginx安装手册.doc

nginx代理概述.doc

Linux文本编辑查找备份等处理

Java+开发环境+jdk1.8+Windows系统搭建开发环境

最新资源

k8s 新版本部署 Ingress-nginx controller.doc