comparison CHANGES @ 470:6866b490272e NGINX_0_7_47

nginx 0.7.47 *) Bugfix: nginx could not be built on FreeBSD 6 and early versions; the bug had appeared in 0.7.46. *) Bugfix: nginx could not be built on MacOSX; the bug had appeared in 0.7.46. *) Bugfix: if the "max_size" parameter was set, then the cache manager might purge a whole cache; the bug had appeared in 0.7.46. *) Change: a segmentation fault might occur in worker process, if the "proxy_cache"/"fastcgi_cache" and the "proxy_cache_valid"/ "fastcgi_cache_valid" were set on different levels; the bug had appeared in 0.7.46. *) Bugfix: a segmentation fault might occur in worker process, if a request was redirected to a proxied or FastCGI server via error_page or try_files; the bug had appeared in 0.7.44.
author Igor Sysoev <http://sysoev.ru>
date Wed, 01 Apr 2009 00:00:00 +0400
parents 56baf312c1b5
children 09f0ef15d544
comparison
equal deleted inserted replaced
469:3174b44e74fc 470:6866b490272e
1
2 Changes with nginx 0.7.47 01 Apr 2009
3
4 *) Bugfix: nginx could not be built on FreeBSD 6 and early versions;
5 the bug had appeared in 0.7.46.
6
7 *) Bugfix: nginx could not be built on MacOSX; the bug had
8 appeared in 0.7.46.
9
10 *) Bugfix: if the "max_size" parameter was set, then the cache manager
11 might purge a whole cache; the bug had appeared in 0.7.46.
12
13 *) Change: a segmentation fault might occur in worker process, if the
14 "proxy_cache"/"fastcgi_cache" and the "proxy_cache_valid"/
15 "fastcgi_cache_valid" were set on different levels; the bug had
16 appeared in 0.7.46.
17
18 *) Bugfix: a segmentation fault might occur in worker process, if a
19 request was redirected to a proxied or FastCGI server via error_page
20 or try_files; the bug had appeared in 0.7.44.
21
1 22
2 Changes with nginx 0.7.46 30 Mar 2009 23 Changes with nginx 0.7.46 30 Mar 2009
3 24
4 *) Bugfix: the previous release tarball was incorrect. 25 *) Bugfix: the previous release tarball was incorrect.
5 26
6 27
7 Changes with nginx 0.7.45 30 Mar 2009 28 Changes with nginx 0.7.45 30 Mar 2009
8 29
9 *) Change: now the "proxy_cache" and the "proxy_cache_valid" can be set 30 *) Change: now the "proxy_cache" and the "proxy_cache_valid" directives
10 on different levels. 31 can be set on different levels.
11 32
12 *) Change: the "clean_time" parameter of the "proxy_cache_path" 33 *) Change: the "clean_time" parameter of the "proxy_cache_path"
13 directive is canceled. 34 directive is canceled.
14 35
15 *) Feature: the "max_size" parameter of the "proxy_cache_path" 36 *) Feature: the "max_size" parameter of the "proxy_cache_path"