Mercurial > hg > nginx-vendor-current

comparison CHANGES @ 656:9d21dad0b5a1 NGINX_1_1_12

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
nginx 1.1.12 *) 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.
author Igor Sysoev <http://sysoev.ru>
date Mon, 26 Dec 2011 00:00:00 +0400
parents 753f505670e0
children 5a4401b9551b
comparison
equal deleted inserted replaced
655:189afff6503f 656:9d21dad0b5a1
1
2 Changes with nginx 1.1.12 26 Dec 2011
3
4 *) Change: a "proxy_pass" directive without URI part now uses changed
5 URI after redirection with the "error_page" directive;
6 Thanks to Lanshun Zhou.
7
8 *) Feature: the "proxy/fastcgi/scgi/uwsgi_cache_lock",
9 "proxy/fastcgi/scgi/uwsgi_cache_lock_timeout" directives.
10
11 *) Feature: the "pcre_jit" directive.
12
13 *) Feature: the "if" SSI command supports captures in regular
14 expressions.
15
16 *) Bugfix: the "if" SSI command did not work inside the "block" command.
17
18 *) Bugfix: the "limit_conn_log_level" and "limit_req_log_level"
19 directives might not work.
20
21 *) Bugfix: the "limit_rate" directive did not allow to use full
22 throughput, even if limit value was very high.
23
24 *) Bugfix: the "sendfile_max_chunk" directive did not work, if the
25 "limit_rate" directive was used.
26
27 *) Bugfix: a "proxy_pass" directive without URI part always used
28 original request URI if variables were used.
29
30 *) Bugfix: a "proxy_pass" directive without URI part might use original
31 request after redirection with the "try_files" directive;
32 Thanks to Lanshun Zhou.
33
34 *) Bugfix: in the ngx_http_scgi_module.
35
36 *) Bugfix: in the ngx_http_mp4_module.
37
38 *) Bugfix: nginx could not be built on Solaris; the bug had appeared in
39 1.1.9.
40
1 41
2 Changes with nginx 1.1.11 12 Dec 2011 42 Changes with nginx 1.1.11 12 Dec 2011
3 43
4 *) Feature: the "so_keepalive" parameter of the "listen" directive. 44 *) Feature: the "so_keepalive" parameter of the "listen" directive.
5 Thanks to Vsevolod Stakhov. 45 Thanks to Vsevolod Stakhov.
4562 *) Feature: the "log_format" supports the variables in the $name form. 4602 *) Feature: the "log_format" supports the variables in the $name form.
4563 4603
4564 *) Bugfix: if at least in one server was no the "listen" directive, then 4604 *) Bugfix: if at least in one server was no the "listen" directive, then
4565 nginx did not listen on the 80 port; the bug had appeared in 0.3.3. 4605 nginx did not listen on the 80 port; the bug had appeared in 0.3.3.
4566 4606
4567 *) Bugfix: if the URI part is omitted in "proxy_pass" directive, the the 4607 *) Bugfix: if the URI part is omitted in "proxy_pass" directive, the 80
4568 80 port was always used. 4608 port was always used.
4569 4609
4570 4610
4571 Changes with nginx 0.3.5 21 Oct 2005 4611 Changes with nginx 0.3.5 21 Oct 2005
4572 4612
4573 *) Bugfix: the segmentation fault may occurred if the IMAP/POP3 login 4613 *) Bugfix: the segmentation fault may occurred if the IMAP/POP3 login
4808 to a server. 4848 to a server.
4809 4849
4810 *) Bugfix: the segmentation fault occurred or the worker process may got 4850 *) Bugfix: the segmentation fault occurred or the worker process may got
4811 caught in an endless loop if the proxied or FastCGI server sent the 4851 caught in an endless loop if the proxied or FastCGI server sent the
4812 "Cache-Control" header line and the "expires" directive was used; in 4852 "Cache-Control" header line and the "expires" directive was used; in
4813 the proxied mode the the bug had appeared in 0.1.29. 4853 the proxied mode the bug had appeared in 0.1.29.
4814 4854
4815 4855
4816 Changes with nginx 0.1.42 23 Aug 2005 4856 Changes with nginx 0.1.42 23 Aug 2005
4817 4857
4818 *) Bugfix: if the request URI had a zero length after the processing in 4858 *) Bugfix: if the request URI had a zero length after the processing in
4883 login state. 4923 login state.
4884 4924
4885 4925
4886 Changes with nginx 0.1.38 08 Jul 2005 4926 Changes with nginx 0.1.38 08 Jul 2005
4887 4927
4888 *) Feature: the "limit_rate" directive is supported in in proxy and 4928 *) Feature: the "limit_rate" directive is supported in proxy and FastCGI
4889 FastCGI mode. 4929 mode.
4890 4930
4891 *) Feature: the "X-Accel-Limit-Rate" response header line is supported 4931 *) Feature: the "X-Accel-Limit-Rate" response header line is supported
4892 in proxy and FastCGI mode. 4932 in proxy and FastCGI mode.
4893 4933
4894 *) Feature: the "break" directive. 4934 *) Feature: the "break" directive.
5036 5076
5037 *) Bugfix: the response encrypted by SSL may not transferred complete. 5077 *) Bugfix: the response encrypted by SSL may not transferred complete.
5038 5078
5039 *) Bugfix: if the length of the response part received at once from 5079 *) Bugfix: if the length of the response part received at once from
5040 proxied or FastCGI server was equal to 500, then nginx returns the 5080 proxied or FastCGI server was equal to 500, then nginx returns the
5041 500 response code; in proxy mode the the bug had appeared in 0.1.29 5081 500 response code; in proxy mode the bug had appeared in 0.1.29 only.
5042 only.
5043 5082
5044 *) Bugfix: nginx did not consider the directives with 8 or 9 parameters 5083 *) Bugfix: nginx did not consider the directives with 8 or 9 parameters
5045 as invalid. 5084 as invalid.
5046 5085
5047 *) Feature: the "return" directive can return the 204 response code. 5086 *) Feature: the "return" directive can return the 204 response code.
5280 *) Bugfix: now, if request contains the zero, then the 404 error is 5319 *) Bugfix: now, if request contains the zero, then the 404 error is
5281 returned for the local requests. 5320 returned for the local requests.
5282 5321
5283 *) Bugfix: nginx could not be built on NetBSD 2.0. 5322 *) Bugfix: nginx could not be built on NetBSD 2.0.
5284 5323
5285 *) Bugfix: the timeout may occur while reading of the the client request 5324 *) Bugfix: the timeout may occur while reading of the client request
5286 body via SSL connections. 5325 body via SSL connections.
5287 5326
5288 5327
5289 Changes with nginx 0.1.18 09 Feb 2005 5328 Changes with nginx 0.1.18 09 Feb 2005
5290 5329