分类： 技术文章

最近测试，用到了这个，给大家个资源，请勿用于商业环境，谢谢！

Changes with nginx 1.1.14                                        30 Jan 2012
) Feature: multiple "limit_req" limits may be used simultaneously.
) Bugfix: in error handling while connecting to a backend.        Thanks to Piotr Sikora.
) Bugfix: in AIO error handling on FreeBSD.
) Bugfix: in the OpenSSL library initialization.
) Bugfix: the "proxy_redirect" directives might not be correctly        inherited.
) Bugfix: memory leak during reconfiguration if the "pcre_jit"        directive was used.

Changes with nginx 1.1.13                                        16 Jan 2012

    *) Feature: the "TLSv1.1" and "TLSv1.2" parameters of the
       "ssl_protocols" directive.

    *) Bugfix: the "limit_req" directive parameters were not inherited
       correctly; the bug had appeared in 1.1.12.

    *) Bugfix: the "proxy_redirect" directive incorrectly processed
       "Refresh" header if regular expression were used.

    *) Bugfix: the "proxy_cache_use_stale" directive with "error" parameter
       did not return answer from cache if there were no live upstreams.

    *) Bugfix: the "worker_cpu_affinity" directive might not work.

    *) Bugfix: nginx could not be built on Solaris; the bug had appeared in
       1.1.12.

    *) Bugfix: in the ngx_http_mp4_module.

基本上还是一个BUG修复版本

Changes with nginx 1.1.12                                        26 Dec 2011

*) Change: a "proxy_pass" directive without URI part now uses changed
URI after redirection with the "error_page" directive;
Thanks to Lanshun Zhou.

*) Feature: the "proxy/fastcgi/scgi/uwsgi_cache_lock",
"proxy/fastcgi/scgi/uwsgi_cache_lock_timeout" directives.

*) Feature: the "pcre_jit" directive.

*) Feature: the "if" SSI command supports captures in regular
expressions.

*) Bugfix: the "if" SSI command did not work inside the "block" command.

*) Bugfix: the "limit_conn_log_level" and "limit_req_log_level"
directives might not work.

*) Bugfix: the "limit_rate" directive did not allow to use full
throughput, even if limit value was very high.

*) Bugfix: the "sendfile_max_chunk" directive did not work, if the
"limit_rate" directive was used.

*) Bugfix: a "proxy_pass" directive without URI part always used
original request URI if variables were used.

*) Bugfix: a "proxy_pass" directive without URI part might use original
request after redirection with the "try_files" directive;
Thanks to Lanshun Zhou.

*) Bugfix: in the ngx_http_scgi_module.

*) Bugfix: in the ngx_http_mp4_module.

*) Bugfix: nginx could not be built on Solaris; the bug had appeared in
1.1.9.

Changes with nginx 1.1.11                                        12 Dec 2011

*) Feature: the "so_keepalive" parameter of the "listen" directive.
Thanks to Vsevolod Stakhov.

*) Feature: the "if_not_empty" parameter of the
"fastcgi/scgi/uwsgi_param" directives.

*) Feature: the $https variable.

*) Feature: the "proxy_redirect" directive supports variables in the
first parameter.

*) Feature: the "proxy_redirect" directive supports regular expressions.

*) Bugfix: the $sent_http_cache_control variable might contain a wrong
value if the "expires" directive was used.
Thanks to Yichun Zhang.

*) Bugfix: the "read_ahead" directive might not work combined with
"try_files" and "open_file_cache".

*) Bugfix: a segmentation fault might occur in a worker process if small
time was used in the "inactive" parameter of the "proxy_cache_path"
directive.

*) Bugfix: responses from cache might hang.

这个问号有两层意思

一为匹配前面的子表达式零次或一次。例如，"do(es)?" 可以匹配 "do" 或 "does" 中的"do" 。? 等价于 {0,1}。

二为当该字符紧跟在任何一个其他限制符 (*, +, ?, {n}, {n,}, {n,m})
后面时，匹配模式是非贪婪的。非贪婪模式尽可能少的匹配所搜索的字符串，而默认的贪婪模式则尽可能多的匹配所搜索的字符串。例如，对于字符串 "oooo"，’o+?’ 将匹配单个 "o"，而 ‘o+’ 将匹配所有 ‘o’。

所以 （.*?）中问号的含义应匹配第二种解释，就是非贪婪模式，最小匹配原则

手持GPS可以记录路线，出路书给其他驴友，不过价格不菲，好的都需要1000多大米，没关系，现在是智能手机时代，我的手机系统是安卓的，可以下载GPS2GE，记录路线，生成KML文件，直接导进GOOGLE EARTH,生成路书，并可以配上路上的图片，现在手机像素都很高了，手机拍相机拍都可以。

我早上上班的测试

Changes with nginx 1.1.10                                        30 Nov 2011

    *) Bugfix: a segmentation fault occured in a worker process if AIO was
       used on Linux; the bug had appeared in 1.1.9.