Mercurial > hg > nginx-site
comparison text/en/CHANGES @ 929:31ed5c0a348b
nginx-1.5.1
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Tue, 04 Jun 2013 17:38:50 +0400 |
parents | 012feca3d85f |
children | edc2c630ba62 |
comparison
equal
deleted
inserted
replaced
928:b568f0c47599 | 929:31ed5c0a348b |
---|---|
1 | |
2 Changes with nginx 1.5.1 04 Jun 2013 | |
3 | |
4 *) Feature: the "ssi_last_modified", "sub_filter_last_modified", and | |
5 "xslt_last_modified" directives. | |
6 Thanks to Alexey Kolpakov. | |
7 | |
8 *) Feature: the "http_403" parameter of the "proxy_next_upstream", | |
9 "fastcgi_next_upstream", "scgi_next_upstream", and | |
10 "uwsgi_next_upstream" directives. | |
11 | |
12 *) Feature: the "allow" and "deny" directives now support unix domain | |
13 sockets. | |
14 | |
15 *) Bugfix: nginx could not be built with the ngx_mail_ssl_module, but | |
16 without ngx_http_ssl_module; the bug had appeared in 1.3.14. | |
17 | |
18 *) Bugfix: in the "proxy_set_body" directive. | |
19 Thanks to Lanshun Zhou. | |
20 | |
21 *) Bugfix: in the "lingering_time" directive. | |
22 Thanks to Lanshun Zhou. | |
23 | |
24 *) Bugfix: the "fail_timeout" parameter of the "server" directive in the | |
25 "upstream" context might not work if "max_fails" parameter was used; | |
26 the bug had appeared in 1.3.0. | |
27 | |
28 *) Bugfix: a segmentation fault might occur in a worker process if the | |
29 "ssl_stapling" directive was used. | |
30 Thanks to Piotr Sikora. | |
31 | |
32 *) Bugfix: in the mail proxy server. | |
33 Thanks to Filipe Da Silva. | |
34 | |
35 *) Bugfix: nginx/Windows might stop accepting connections if several | |
36 worker processes were used. | |
37 | |
1 | 38 |
2 Changes with nginx 1.5.0 07 May 2013 | 39 Changes with nginx 1.5.0 07 May 2013 |
3 | 40 |
4 *) Security: a stack-based buffer overflow might occur in a worker | 41 *) Security: a stack-based buffer overflow might occur in a worker |
5 process while handling a specially crafted request, potentially | 42 process while handling a specially crafted request, potentially |