Mercurial > hg > nginx-vendor-current
diff CHANGES @ 636:943566b4d82e NGINX_1_1_2
nginx 1.1.2
*) Change: now if total size of all ranges is greater than source
response size, then nginx disables ranges and returns just the source
response.
*) Feature: the "max_ranges" directive.
*) Bugfix: the "ssl_verify_client", "ssl_verify_depth", and
"ssl_prefer_server_ciphers" directives might work incorrectly if SNI
was used.
*) Bugfix: in the "proxy/fastcgi/scgi/uwsgi_ignore_client_abort"
directives.
| author | Igor Sysoev <http://sysoev.ru> |
|---|---|
| date | Mon, 05 Sep 2011 00:00:00 +0400 |
| parents | 23ef0645ea57 |
| children | f5a8cf31a203 |
line wrap: on
line diff
--- a/CHANGES +++ b/CHANGES @@ -1,43 +1,57 @@ +Changes with nginx 1.1.2 05 Sep 2011 + + *) Change: now if total size of all ranges is greater than source + response size, then nginx disables ranges and returns just the source + response. + + *) Feature: the "max_ranges" directive. + + *) Bugfix: the "ssl_verify_client", "ssl_verify_depth", and + "ssl_prefer_server_ciphers" directives might work incorrectly if SNI + was used. + + *) Bugfix: in the "proxy/fastcgi/scgi/uwsgi_ignore_client_abort" + directives. + + Changes with nginx 1.1.1 22 Aug 2011 - *) Change: now cache loader processes either as many files as specified - by "loader_files" parameter or works no more than time specified by - "loader_threshold" parameter during each iteration. - - *) Change: now SIGWINCH signal works only in deamon mode. - - *) Feature: now shared zones and caches use POSIX semaphores on - Solaris. + *) Change: now cache loader processes either as many files as specified + by "loader_files" parameter or works no longer than time specified by + the "loader_threshold" parameter during each iteration. + + *) Change: now SIGWINCH signal works only in daemon mode. + + *) Feature: now shared zones and caches use POSIX semaphores on Solaris. Thanks to Den Ivanov. *) Feature: accept filters are now supported on NetBSD. - *) Bugfix: nginx could not be build on Linux 3.0. - - *) Bugfix: nginx did not use gzipping in some cases; the bug had + *) Bugfix: nginx could not be built on Linux 3.0. + + *) Bugfix: nginx did not use gzipping in some cases; the bug had appeared in 1.1.0. - *) Bugfix: request body might be incorrectly processed if client used + *) Bugfix: request body might be processed incorrectly if client used pipelining. *) Bugfix: in the "request_body_in_single_buf" directive. - *) Bugfix: in "proxy_set_body" and "proxy_pass_request_body" directives + *) Bugfix: in "proxy_set_body" and "proxy_pass_request_body" directives if SSL connection to backend was used. - *) Bugfix: nginx hogged CPU if all servers in an upstream were marked - as "down". - - *) Bugfix: a segmentation fault might occur during reconfiguration if - ssl_session_cache was defined but not used in a previous - configuration. - - *) Bugfix: a segmentation fault might occur in a worker process if many + *) Bugfix: nginx hogged CPU if all servers in an upstream were marked as + "down". + + *) Bugfix: a segmentation fault might occur during reconfiguration if + ssl_session_cache was defined but not used in previous configuration. + + *) Bugfix: a segmentation fault might occur in a worker process if many backup servers were used in an upstream. - *) Bugfix: a segmentation fault might occur in a worker process if - "fastcgi/scgi/uwsgi_param" directives were used with values starting + *) Bugfix: a segmentation fault might occur in a worker process if + "fastcgi/scgi/uwsgi_param" directives were used with values starting with "HTTP_"; the bug had appeared in 0.8.40. @@ -45,10 +59,10 @@ Changes with nginx 1.1.0 *) Feature: cache loader run time decrease. - *) Feature: "loader_files", "loader_sleep", and "loader_threshold" + *) Feature: "loader_files", "loader_sleep", and "loader_threshold" options of the "proxy/fastcgi/scgi/uwsgi_cache_path" directives. - *) Feature: loading time decrease of configuration with large number of + *) Feature: loading time decrease of configuration with large number of HTTPS sites. *) Feature: now nginx supports ECDHE key exchange ciphers. @@ -60,24 +74,24 @@ Changes with nginx 1.1.0 *) Bugfix: in closing connection for pipelined requests. Thanks to Maxim Dounin. - *) Bugfix: nginx did not disable gzipping if client sent "gzip;q=0" in + *) Bugfix: nginx did not disable gzipping if client sent "gzip;q=0" in "Accept-Encoding" request header line. *) Bugfix: in timeout in unbuffered proxied mode. Thanks to Maxim Dounin. - *) Bugfix: memory leaks when a "proxy_pass" directive contains - variables and proxies to an HTTPS backend. + *) Bugfix: memory leaks when a "proxy_pass" directive contains variables + and proxies to an HTTPS backend. Thanks to Maxim Dounin. - *) Bugfix: in parameter validaiton of a "proxy_pass" directive with + *) Bugfix: in parameter validaiton of a "proxy_pass" directive with variables. Thanks to Lanshun Zhou. *) Bugfix: SSL did not work on QNX. Thanks to Maxim Dounin. - *) Bugfix: SSL modules could not be built by gcc 4.6 without + *) Bugfix: SSL modules could not be built by gcc 4.6 without --with-debug option. @@ -86,18 +100,18 @@ Changes with nginx 1.0.5 *) Change: now default SSL ciphers are "HIGH:!aNULL:!MD5". Thanks to Rob Stradling. - *) Feature: the "referer_hash_max_size" and "referer_hash_bucket_size" + *) Feature: the "referer_hash_max_size" and "referer_hash_bucket_size" directives. Thanks to Witold Filipczyk. *) Feature: $uid_reset variable. - *) Bugfix: a segmentation fault might occur in a worker process, if a + *) Bugfix: a segmentation fault might occur in a worker process, if a caching was used. Thanks to Lanshun Zhou. - *) Bugfix: worker processes may got caught in an endless loop during - reconfiguration, if a caching was used; the bug had appeared in + *) Bugfix: worker processes may got caught in an endless loop during + reconfiguration, if a caching was used; the bug had appeared in 0.8.48. Thanks to Maxim Dounin. @@ -107,81 +121,81 @@ Changes with nginx 1.0.5 Changes with nginx 1.0.4 01 Jun 2011 - *) Change: now regular expressions case sensitivity in the "map" + *) Change: now regular expressions case sensitivity in the "map" directive is given by prefixes "~" or "~*". - *) Feature: now shared zones and caches use POSIX semaphores on Linux. + *) Feature: now shared zones and caches use POSIX semaphores on Linux. Thanks to Denis F. Latypoff. *) Bugfix: "stalled cache updating" alert. - *) Bugfix: nginx could not be built --without-http_auth_basic_module; + *) Bugfix: nginx could not be built --without-http_auth_basic_module; the bug had appeared in 1.0.3. Changes with nginx 1.0.3 25 May 2011 - *) Feature: the "auth_basic_user_file" directive supports "$apr1", + *) Feature: the "auth_basic_user_file" directive supports "$apr1", "{PLAIN}", and "{SSHA}" password encryption methods. Thanks to Maxim Dounin. *) Feature: the "geoip_org" directive and $geoip_org variable. Thanks to Alexander Uskov, Arnaud Granal, and Denis F. Latypoff. - *) Feature: ngx_http_geo_module and ngx_http_geoip_module support IPv4 + *) Feature: ngx_http_geo_module and ngx_http_geoip_module support IPv4 addresses mapped to IPv6 addresses. - *) Bugfix: a segmentation fault occurred in a worker process during - testing IPv4 address mapped to IPv6 address, if access or deny rules + *) Bugfix: a segmentation fault occurred in a worker process during + testing IPv4 address mapped to IPv6 address, if access or deny rules were defined only for IPv6; the bug had appeared in 0.8.22. - *) Bugfix: a cached response may be broken if "proxy/fastcgi/scgi/ - uwsgi_cache_bypass" and "proxy/fastcgi/scgi/uwsgi_no_cache" - directive values were different; the bug had appeared in 0.8.46. + *) Bugfix: a cached response may be broken if "proxy/fastcgi/scgi/ + uwsgi_cache_bypass" and "proxy/fastcgi/scgi/uwsgi_no_cache" directive + values were different; the bug had appeared in 0.8.46. Changes with nginx 1.0.2 10 May 2011 *) Feature: now shared zones and caches use POSIX semaphores. - *) Bugfix: in the "rotate" parameter of the "image_filter" directive. + *) Bugfix: in the "rotate" parameter of the "image_filter" directive. Thanks to Adam Bocim. - *) Bugfix: nginx could not be built on Solaris; the bug had appeared in + *) Bugfix: nginx could not be built on Solaris; the bug had appeared in 1.0.1. Changes with nginx 1.0.1 03 May 2011 - *) Change: now the "split_clients" directive uses MurmurHash2 algorithm + *) Change: now the "split_clients" directive uses MurmurHash2 algorithm because of better distribution. Thanks to Oleg Mamontov. - *) Change: now long strings starting with zero are not considered as + *) Change: now long strings starting with zero are not considered as false values. Thanks to Maxim Dounin. *) Change: now nginx uses a default listen backlog value 511 on Linux. - *) Feature: the $upstream_... variables may be used in the SSI and perl + *) Feature: the $upstream_... variables may be used in the SSI and perl modules. *) Bugfix: now nginx limits better disk cache size. Thanks to Oleg Mamontov. - *) Bugfix: a segmentation fault might occur while parsing incorrect - IPv4 address; the bug had appeared in 0.9.3. + *) Bugfix: a segmentation fault might occur while parsing incorrect IPv4 + address; the bug had appeared in 0.9.3. Thanks to Maxim Dounin. - *) Bugfix: nginx could not be built by gcc 4.6 without --with-debug + *) Bugfix: nginx could not be built by gcc 4.6 without --with-debug option. - *) Bugfix: nginx could not be built on Solaris 9 and earlier; the bug + *) Bugfix: nginx could not be built on Solaris 9 and earlier; the bug had appeared in 0.9.3. Thanks to Dagobert Michelsen. - *) Bugfix: $request_time variable had invalid values if subrequests - were used; the bug had appeared in 0.8.47. + *) Bugfix: $request_time variable had invalid values if subrequests were + used; the bug had appeared in 0.8.47. Thanks to Igor A. Valcov. @@ -190,7 +204,7 @@ Changes with nginx 1.0.0 *) Bugfix: a cache manager might hog CPU after reload. Thanks to Maxim Dounin. - *) Bugfix: an "image_filter crop" directive worked incorrectly coupled + *) Bugfix: an "image_filter crop" directive worked incorrectly coupled with an "image_filter rotate 180" directive. *) Bugfix: a "satisfy any" directive disabled custom 401 error page. @@ -198,22 +212,22 @@ Changes with nginx 1.0.0 Changes with nginx 0.9.7 04 Apr 2011 - *) Feature: now keepalive connections may be closed premature, if there + *) Feature: now keepalive connections may be closed premature, if there are no free worker connections. Thanks to Maxim Dounin. *) Feature: the "rotate" parameter of the "image_filter" directive. Thanks to Adam Bocim. - *) Bugfix: a case when a backend in "fastcgi_pass", "scgi_pass", or - "uwsgi_pass" directives is given by expression and refers to a + *) Bugfix: a case when a backend in "fastcgi_pass", "scgi_pass", or + "uwsgi_pass" directives is given by expression and refers to a defined upstream. Changes with nginx 0.9.6 21 Mar 2011 - *) Feature: the "map" directive supports regular expressions as value - of the first parameter. + *) Feature: the "map" directive supports regular expressions as value of + the first parameter. *) Feature: $time_iso8601 access_log variable. Thanks to Michael Lustfield. @@ -221,19 +235,19 @@ Changes with nginx 0.9.6 Changes with nginx 0.9.5 21 Feb 2011 - *) Change: now nginx uses a default listen backlog value -1 on Linux. + *) Change: now nginx uses a default listen backlog value -1 on Linux. Thanks to Andrei Nigmatulin. - *) Feature: the "utf8" parameter of "geoip_country" and "geoip_city" + *) Feature: the "utf8" parameter of "geoip_country" and "geoip_city" directives. Thanks to Denis F. Latypoff. - *) Bugfix: in a default "proxy_redirect" directive if "proxy_pass" + *) Bugfix: in a default "proxy_redirect" directive if "proxy_pass" directive has no URI part. Thanks to Maxim Dounin. - *) Bugfix: an "error_page" directive did not work with nonstandard - error codes; the bug had appeared in 0.8.53. + *) Bugfix: an "error_page" directive did not work with nonstandard error + codes; the bug had appeared in 0.8.53. Thanks to Maxim Dounin. @@ -246,23 +260,23 @@ Changes with nginx 0.9.4 Changes with nginx 0.9.3 13 Dec 2010 - *) Bugfix: if there was a single server for given IPv6 address:port - pair, then captures in regular expressions in a "server_name" + *) Bugfix: if there was a single server for given IPv6 address:port + pair, then captures in regular expressions in a "server_name" directive did not work. - *) Bugfix: nginx could not be built on Solaris; the bug had appeared in + *) Bugfix: nginx could not be built on Solaris; the bug had appeared in 0.9.0. Changes with nginx 0.9.2 06 Dec 2010 - *) Feature: the "If-Unmodified-Since" client request header line + *) Feature: the "If-Unmodified-Since" client request header line support. - *) Workaround: fallback to accept() syscall if accept4() was not + *) Workaround: fallback to accept() syscall if accept4() was not implemented; the issue had appeared in 0.9.0. - *) Bugfix: nginx could not be built on Cygwin; the bug had appeared in + *) Bugfix: nginx could not be built on Cygwin; the bug had appeared in 0.9.0. *) Bugfix: for OpenSSL vulnerability CVE-2010-4180. @@ -271,7 +285,7 @@ Changes with nginx 0.9.2 Changes with nginx 0.9.1 30 Nov 2010 - *) Bugfix: "return CODE message" directives did not work; the bug had + *) Bugfix: "return CODE message" directives did not work; the bug had appeared in 0.9.0. @@ -279,13 +293,13 @@ Changes with nginx 0.9.0 *) Feature: the "keepalive_disable" directive. - *) Feature: the "map" directive supports variables as value of a - defined variable. - - *) Feature: the "map" directive supports empty strings as value of the + *) Feature: the "map" directive supports variables as value of a defined + variable. + + *) Feature: the "map" directive supports empty strings as value of the first parameter. - *) Feature: the "map" directive supports expressions as the first + *) Feature: the "map" directive supports expressions as the first parameter. *) Feature: nginx(8) manual page. @@ -294,36 +308,36 @@ Changes with nginx 0.9.0 *) Feature: Linux accept4() support. Thanks to Simon Liu. - *) Workaround: elimination of Linux linker warning about "sys_errlist" + *) Workaround: elimination of Linux linker warning about "sys_errlist" and "sys_nerr"; the warning had appeared in 0.8.35. - *) Bugfix: a segmentation fault might occur in a worker process, if the + *) Bugfix: a segmentation fault might occur in a worker process, if the "auth_basic" directive was used. Thanks to Michail Laletin. - *) Bugfix: compatibility with ngx_http_eval_module; the bug had - appeared in 0.8.42. + *) Bugfix: compatibility with ngx_http_eval_module; the bug had appeared + in 0.8.42. Changes with nginx 0.8.53 18 Oct 2010 - *) Feature: now the "error_page" directive allows to change a status + *) Feature: now the "error_page" directive allows to change a status code in a redirect. - *) Feature: the "gzip_disable" directive supports special "degradation" + *) Feature: the "gzip_disable" directive supports special "degradation" mask. *) Bugfix: a socket leak might occurred if file AIO was used. Thanks to Maxim Dounin. - *) Bugfix: if the first server had no "listen" directive and there was - no explicit default server, then a next server with a "listen" + *) Bugfix: if the first server had no "listen" directive and there was + no explicit default server, then a next server with a "listen" directive became the default server; the bug had appeared in 0.8.21. Changes with nginx 0.8.52 28 Sep 2010 - *) Bugfix: nginx used SSL mode for a listen socket if any listen option + *) Bugfix: nginx used SSL mode for a listen socket if any listen option was set; the bug had appeared in 0.8.51. @@ -331,75 +345,75 @@ Changes with nginx 0.8.51 *) Change: the "secure_link_expires" directive has been canceled. - *) Change: a logging level of resolver errors has been lowered from + *) Change: a logging level of resolver errors has been lowered from "alert" to "error". - *) Feature: now a listen socket "ssl" parameter may be set several + *) Feature: now a listen socket "ssl" parameter may be set several times. Changes with nginx 0.8.50 02 Sep 2010 - *) Feature: the "secure_link", "secure_link_md5", and + *) Feature: the "secure_link", "secure_link_md5", and "secure_link_expires" directives of the ngx_http_secure_link_module. *) Feature: the -q switch. Thanks to Gena Makhomed. - *) Bugfix: worker processes may got caught in an endless loop during - reconfiguration, if a caching was used; the bug had appeared in + *) Bugfix: worker processes may got caught in an endless loop during + reconfiguration, if a caching was used; the bug had appeared in 0.8.48. *) Bugfix: in the "gzip_disable" directive. Thanks to Derrick Petzold. - *) Bugfix: nginx/Windows could not send stop, quit, reopen, and reload + *) Bugfix: nginx/Windows could not send stop, quit, reopen, and reload signals to a process run in other session. Changes with nginx 0.8.49 09 Aug 2010 - *) Feature: the "image_filter_jpeg_quality" directive supports + *) Feature: the "image_filter_jpeg_quality" directive supports variables. - *) Bugfix: a segmentation fault might occur in a worker process, if the - $geoip_region_name variables was used; the bug had appeared in + *) Bugfix: a segmentation fault might occur in a worker process, if the + $geoip_region_name variables was used; the bug had appeared in 0.8.48. - *) Bugfix: errors intercepted by error_page were cached only for next + *) Bugfix: errors intercepted by error_page were cached only for next request; the bug had appeared in 0.8.48. Changes with nginx 0.8.48 03 Aug 2010 - *) Change: now the "server_name" directive default value is an empty + *) Change: now the "server_name" directive default value is an empty name "". Thanks to Gena Makhomed. - *) Change: now the "server_name_in_redirect" directive default value is + *) Change: now the "server_name_in_redirect" directive default value is "off". - *) Feature: the $geoip_dma_code, $geoip_area_code, and + *) Feature: the $geoip_dma_code, $geoip_area_code, and $geoip_region_name variables. Thanks to Christine McGonagle. - *) Bugfix: the "proxy_pass", "fastcgi_pass", "uwsgi_pass", and - "scgi_pass" directives were not inherited inside "limit_except" + *) Bugfix: the "proxy_pass", "fastcgi_pass", "uwsgi_pass", and + "scgi_pass" directives were not inherited inside "limit_except" blocks. - *) Bugfix: the "proxy_cache_min_uses", "fastcgi_cache_min_uses" - "uwsgi_cache_min_uses", and "scgi_cache_min_uses" directives did not + *) Bugfix: the "proxy_cache_min_uses", "fastcgi_cache_min_uses" + "uwsgi_cache_min_uses", and "scgi_cache_min_uses" directives did not work; the bug had appeared in 0.8.46. - *) Bugfix: the "fastcgi_split_path_info" directive used incorrectly + *) Bugfix: the "fastcgi_split_path_info" directive used incorrectly captures, if only parts of an URI were captured. Thanks to Yuriy Taraday and Frank Enderle. - *) Bugfix: the "rewrite" directive did not escape a ";" character - during copying from URI to query string. + *) Bugfix: the "rewrite" directive did not escape a ";" character during + copying from URI to query string. Thanks to Daisuke Murase. - *) Bugfix: the ngx_http_image_filter_module closed a connection, if an + *) Bugfix: the ngx_http_image_filter_module closed a connection, if an image was larger than "image_filter_buffer" size. @@ -409,22 +423,22 @@ Changes with nginx 0.8.47 *) Bugfix: errors intercepted by error_page could not be cached. - *) Bugfix: a cache manager process may got caught in an endless loop, - if max_size parameter was used; the bug had appeared in 0.8.46. + *) Bugfix: a cache manager process may got caught in an endless loop, if + max_size parameter was used; the bug had appeared in 0.8.46. Changes with nginx 0.8.46 19 Jul 2010 - *) Change: now the "proxy_no_cache", "fastcgi_no_cache", - "uwsgi_no_cache", and "scgi_no_cache" directives affect on a cached + *) Change: now the "proxy_no_cache", "fastcgi_no_cache", + "uwsgi_no_cache", and "scgi_no_cache" directives affect on a cached response saving only. - *) Feature: the "proxy_cache_bypass", "fastcgi_cache_bypass", + *) Feature: the "proxy_cache_bypass", "fastcgi_cache_bypass", "uwsgi_cache_bypass", and "scgi_cache_bypass" directives. - *) Bugfix: nginx did not free memory in cache keys zones if there was - an error during working with backend: the memory was freed only - after inactivity time or on memory low condition. + *) Bugfix: nginx did not free memory in cache keys zones if there was an + error during working with backend: the memory was freed only after + inactivity time or on memory low condition. Changes with nginx 0.8.45 13 Jul 2010 @@ -432,23 +446,23 @@ Changes with nginx 0.8.45 *) Feature: ngx_http_xslt_filter improvements. Thanks to Laurence Rowe. - *) Bugfix: SSI response might be truncated after include with + *) Bugfix: SSI response might be truncated after include with wait="yes"; the bug had appeared in 0.7.25. Thanks to Maxim Dounin. - *) Bugfix: the "listen" directive did not support the "setfib=0" + *) Bugfix: the "listen" directive did not support the "setfib=0" parameter. Changes with nginx 0.8.44 05 Jul 2010 - *) Change: now nginx does not cache by default backend responses, if + *) Change: now nginx does not cache by default backend responses, if they have a "Set-Cookie" header line. *) Feature: the "listen" directive supports the "setfib" parameter. Thanks to Andrew Filonov. - *) Bugfix: the "sub_filter" directive might change character case on + *) Bugfix: the "sub_filter" directive might change character case on partial match. *) Bugfix: compatibility with HP/UX. @@ -463,22 +477,21 @@ Changes with nginx 0.8.43 *) Feature: large geo ranges base loading speed-up. - *) Bugfix: an error_page redirection to "location /zero {return 204;}" - without changing status code kept the error body; the bug had + *) Bugfix: an error_page redirection to "location /zero {return 204;}" + without changing status code kept the error body; the bug had appeared in 0.8.42. - *) Bugfix: nginx might close IPv6 listen socket during - reconfiguration. + *) Bugfix: nginx might close IPv6 listen socket during reconfiguration. Thanks to Maxim Dounin. - *) Bugfix: the $uid_set variable may be used at any request processing + *) Bugfix: the $uid_set variable may be used at any request processing stage. Changes with nginx 0.8.42 21 Jun 2010 - *) Change: now nginx tests locations given by regular expressions, if - request was matched exactly by a location given by a prefix string. + *) Change: now nginx tests locations given by regular expressions, if + request was matched exactly by a location given by a prefix string. The previous behavior has been introduced in 0.7.1. *) Feature: the ngx_http_scgi_module. @@ -489,17 +502,17 @@ Changes with nginx 0.8.42 Changes with nginx 0.8.41 15 Jun 2010 - *) Security: nginx/Windows worker might be terminated abnormally if a + *) Security: nginx/Windows worker might be terminated abnormally if a requested file name has invalid UTF-8 encoding. *) Change: now nginx allows to use spaces in a request line. - *) Bugfix: the "proxy_redirect" directive changed incorrectly a backend + *) Bugfix: the "proxy_redirect" directive changed incorrectly a backend "Refresh" response header line. Thanks to Andrey Andreew and Max Sogin. - *) Bugfix: nginx did not support path without host name in - "Destination" request header line. + *) Bugfix: nginx did not support path without host name in "Destination" + request header line. Changes with nginx 0.8.40 07 Jun 2010 @@ -510,26 +523,26 @@ Changes with nginx 0.8.40 *) Feature: the ngx_http_uwsgi_module. Thanks to Roberto De Ioris. - *) Feature: a "fastcgi_param" directive with value starting with - "HTTP_" overrides a client request header line. - - *) Bugfix: the "If-Modified-Since", "If-Range", etc. client request + *) Feature: a "fastcgi_param" directive with value starting with "HTTP_" + overrides a client request header line. + + *) Bugfix: the "If-Modified-Since", "If-Range", etc. client request header lines were passed to FastCGI-server while caching. - *) Bugfix: listen unix domain socket could not be changed during + *) Bugfix: listen unix domain socket could not be changed during reconfiguration. Thanks to Maxim Dounin. Changes with nginx 0.8.39 31 May 2010 - *) Bugfix: an inherited "alias" directive worked incorrectly in + *) Bugfix: an inherited "alias" directive worked incorrectly in inclusive location. - *) Bugfix: in "alias" with variables and "try_files" directives + *) Bugfix: in "alias" with variables and "try_files" directives combination. - *) Bugfix: listen unix domain and IPv6 sockets did not inherit while + *) Bugfix: listen unix domain and IPv6 sockets did not inherit while online upgrade. Thanks to Maxim Dounin. @@ -538,15 +551,15 @@ Changes with nginx 0.8.38 *) Feature: the "proxy_no_cache" and "fastcgi_no_cache" directives. - *) Feature: now the "rewrite" directive does a redirect automatically - if the $scheme variable is used. + *) Feature: now the "rewrite" directive does a redirect automatically if + the $scheme variable is used. Thanks to Piotr Sikora. - *) Bugfix: now "limit_req" delay directive conforms to the described + *) Bugfix: now "limit_req" delay directive conforms to the described algorithm. Thanks to Maxim Dounin. - *) Bugfix: the $uid_got variable might not be used in the SSI and perl + *) Bugfix: the $uid_got variable might not be used in the SSI and perl modules. @@ -556,31 +569,31 @@ Changes with nginx 0.8.37 *) Feature: the "map" directive supports keys more than 255 characters. - *) Bugfix: nginx ignored the "private" and "no-store" values in the + *) Bugfix: nginx ignored the "private" and "no-store" values in the "Cache-Control" backend response header line. - *) Bugfix: a "stub" parameter of an "include" SSI directive was not + *) Bugfix: a "stub" parameter of an "include" SSI directive was not used, if empty response has 200 status code. - *) Bugfix: if a proxied or FastCGI request was internally redirected to - another proxied or FastCGI location, then a segmentation fault might + *) Bugfix: if a proxied or FastCGI request was internally redirected to + another proxied or FastCGI location, then a segmentation fault might occur in a worker process; the bug had appeared in 0.8.33. Thanks to Yichun Zhang. - *) Bugfix: IMAP connections may hang until they timed out while talking + *) Bugfix: IMAP connections may hang until they timed out while talking to Zimbra server. Thanks to Alan Batie. Changes with nginx 0.8.36 22 Apr 2010 - *) Bugfix: the ngx_http_dav_module handled incorrectly the DELETE, - COPY, and MOVE methods for symlinks. - - *) Bugfix: values of the $query_string, $arg_..., etc. variables cached + *) Bugfix: the ngx_http_dav_module handled incorrectly the DELETE, COPY, + and MOVE methods for symlinks. + + *) Bugfix: values of the $query_string, $arg_..., etc. variables cached in main request were used by the SSI module in subrequests. - *) Bugfix: a variable value was repeatedly encoded after each an "echo" + *) Bugfix: a variable value was repeatedly encoded after each an "echo" SSI-command output; the bug had appeared in 0.6.14. *) Bugfix: a worker process hung if a FIFO file was requested. @@ -589,7 +602,7 @@ Changes with nginx 0.8.36 *) Bugfix: OpenSSL-1.0.0 compatibility on 64-bit Linux. Thanks to Maxim Dounin. - *) Bugfix: nginx could not be built --without-http-cache; the bug had + *) Bugfix: nginx could not be built --without-http-cache; the bug had appeared in 0.8.35. @@ -599,60 +612,60 @@ Changes with nginx 0.8.35 *) Feature: the "chunked_transfer_encoding" directive. - *) Bugfix: an "&" character was not escaped when it was copied in + *) Bugfix: an "&" character was not escaped when it was copied in arguments part in a rewrite rule. - *) Bugfix: nginx might be terminated abnormally while a signal - processing or if the directive "timer_resolution" was used on - platforms which do not support kqueue or eventport notification + *) Bugfix: nginx might be terminated abnormally while a signal + processing or if the directive "timer_resolution" was used on + platforms which do not support kqueue or eventport notification methods. Thanks to George Xie and Maxim Dounin. - *) Bugfix: if temporary files and permanent storage area resided at - different file systems, then permanent file modification times were + *) Bugfix: if temporary files and permanent storage area resided at + different file systems, then permanent file modification times were incorrect. Thanks to Maxim Dounin. - *) Bugfix: ngx_http_memcached_module might issue the error message + *) Bugfix: ngx_http_memcached_module might issue the error message "memcached sent invalid trailer". Thanks to Maxim Dounin. - *) Bugfix: nginx could not built zlib-1.2.4 library using the library + *) Bugfix: nginx could not built zlib-1.2.4 library using the library sources. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault occurred in a worker process, if there - was large stderr output before FastCGI response; the bug had - appeared in 0.8.34. + *) Bugfix: a segmentation fault occurred in a worker process, if there + was large stderr output before FastCGI response; the bug had appeared + in 0.8.34. Thanks to Maxim Dounin. Changes with nginx 0.8.34 03 Mar 2010 - *) Bugfix: nginx did not support all ciphers and digests used in client + *) Bugfix: nginx did not support all ciphers and digests used in client certificates. Thanks to Innocenty Enikeew. - *) Bugfix: nginx cached incorrectly FastCGI responses if there was - large stderr output before response. + *) Bugfix: nginx cached incorrectly FastCGI responses if there was large + stderr output before response. *) Bugfix: nginx did not support HTTPS referrers. - *) Bugfix: nginx/Windows might not find file if path in configuration + *) Bugfix: nginx/Windows might not find file if path in configuration was given in other character case; the bug had appeared in 0.8.33. - *) Bugfix: the $date_local variable has an incorrect value, if the "%s" + *) Bugfix: the $date_local variable has an incorrect value, if the "%s" format was used. Thanks to Maxim Dounin. - *) Bugfix: if ssl_session_cache was not set or was set to "none", then - during client certificate verify the error "session id context + *) Bugfix: if ssl_session_cache was not set or was set to "none", then + during client certificate verify the error "session id context uninitialized" might occur; the bug had appeared in 0.7.1. - *) Bugfix: a geo range returned default value if the range included two + *) Bugfix: a geo range returned default value if the range included two or more /16 networks and did not begin at /16 network boundary. - *) Bugfix: a block used in a "stub" parameter of an "include" SSI + *) Bugfix: a block used in a "stub" parameter of an "include" SSI directive was output with "text/plain" MIME type. *) Bugfix: $r->sleep() did not work; the bug had appeared in 0.8.11. @@ -666,19 +679,19 @@ Changes with nginx 0.8.33 *) Security: now nginx/Windows ignores short files names. Thanks to Dan Crowley, Core Security Technologies. - *) Change: now keepalive connections after POST requests are not + *) Change: now keepalive connections after POST requests are not disabled for MSIE 7.0+. Thanks to Adam Lounds. *) Workaround: now keepalive connections are disabled for Safari. Thanks to Joshua Sierles. - *) Bugfix: if a proxied or FastCGI request was internally redirected to - another proxied or FastCGI location, then $upstream_response_time - variable may have abnormally large value; the bug had appeared in + *) Bugfix: if a proxied or FastCGI request was internally redirected to + another proxied or FastCGI location, then $upstream_response_time + variable may have abnormally large value; the bug had appeared in 0.8.7. - *) Bugfix: a segmentation fault might occur in a worker process, while + *) Bugfix: a segmentation fault might occur in a worker process, while discarding a request body; the bug had appeared in 0.8.11. @@ -687,68 +700,68 @@ Changes with nginx 0.8.32 *) Bugfix: UTF-8 encoding usage in the ngx_http_autoindex_module. Thanks to Maxim Dounin. - *) Bugfix: regular expression named captures worked for two names only. + *) Bugfix: regular expression named captures worked for two names only. Thanks to Maxim Dounin. - *) Bugfix: now the "localhost" name is used in the "Host" request - header line, if an unix domain socket is defined in the "auth_http" + *) Bugfix: now the "localhost" name is used in the "Host" request header + line, if an unix domain socket is defined in the "auth_http" directive. Thanks to Maxim Dounin. - *) Bugfix: nginx did not support chunked transfer encoding for 201 + *) Bugfix: nginx did not support chunked transfer encoding for 201 responses. Thanks to Julian Reich. - *) Bugfix: if the "expires modified" set date in the past, then a - negative number was set in the "Cache-Control" response header line. + *) Bugfix: if the "expires modified" set date in the past, then a + negative number was set in the "Cache-Control" response header line. Thanks to Alex Kapranoff. Changes with nginx 0.8.31 23 Dec 2009 - *) Feature: now the "error_page" directive may redirect the 301 and 302 + *) Feature: now the "error_page" directive may redirect the 301 and 302 responses. - *) Feature: the $geoip_city_continent_code, $geoip_latitude, and + *) Feature: the $geoip_city_continent_code, $geoip_latitude, and $geoip_longitude variables. Thanks to Arvind Sundararajan. - *) Feature: now the ngx_http_image_filter_module deletes always EXIF - and other application specific data if the data consume more than 5% - of a JPEG file. - - *) Bugfix: nginx closed a connection if a cached response had an empty + *) Feature: now the ngx_http_image_filter_module deletes always EXIF and + other application specific data if the data consume more than 5% of a + JPEG file. + + *) Bugfix: nginx closed a connection if a cached response had an empty body. Thanks to Piotr Sikora. - *) Bugfix: nginx might not be built by gcc 4.x if the -O2 or higher + *) Bugfix: nginx might not be built by gcc 4.x if the -O2 or higher optimization option was used. Thanks to Maxim Dounin and Denis F. Latypoff. - *) Bugfix: regular expressions in location were always tested in + *) Bugfix: regular expressions in location were always tested in case-sensitive mode; the bug had appeared in 0.8.25. - *) Bugfix: nginx cached a 304 response if there was the "If-None-Match" + *) Bugfix: nginx cached a 304 response if there was the "If-None-Match" header line in a proxied request. Thanks to Tim Dettrick and David Kostal. - *) Bugfix: nginx/Windows tried to delete a temporary file twice if the + *) Bugfix: nginx/Windows tried to delete a temporary file twice if the file should replace an already existent file. Changes with nginx 0.8.30 15 Dec 2009 - *) Change: now the default buffer size of the + *) Change: now the default buffer size of the "large_client_header_buffers" directive is 8K. Thanks to Andrew Cholakian. *) Feature: the conf/fastcgi.conf for simple FastCGI configurations. - *) Bugfix: nginx/Windows tried to rename a temporary file twice if the + *) Bugfix: nginx/Windows tried to rename a temporary file twice if the file should replace an already existent file. - *) Bugfix: of "double free or corruption" error issued if host could - not be resolved; the bug had appeared in 0.8.22. + *) Bugfix: of "double free or corruption" error issued if host could not + be resolved; the bug had appeared in 0.8.22. Thanks to Konstantin Svist. *) Bugfix: in libatomic usage on some platforms. @@ -757,11 +770,11 @@ Changes with nginx 0.8.30 Changes with nginx 0.8.29 30 Nov 2009 - *) Change: now the "009" status code is written to an access log for + *) Change: now the "009" status code is written to an access log for proxied HTTP/0.9 responses. - *) Feature: the "addition_types", "charset_types", "gzip_types", - "ssi_types", "sub_filter_types", and "xslt_types" directives support + *) Feature: the "addition_types", "charset_types", "gzip_types", + "ssi_types", "sub_filter_types", and "xslt_types" directives support an "*" parameter. *) Feature: GCC 4.1+ built-in atomic operations usage. @@ -774,63 +787,63 @@ Changes with nginx 0.8.29 *) Bugfix: cached HTTP/0.9 responses were handled incorrectly. - *) Bugfix: regular expression named captures given by "?P<...>" did not + *) Bugfix: regular expression named captures given by "?P<...>" did not work in a "server_name" directive. Thanks to Maxim Dounin. Changes with nginx 0.8.28 23 Nov 2009 - *) Bugfix: nginx could not be built with the --without-pcre parameter; + *) Bugfix: nginx could not be built with the --without-pcre parameter; the bug had appeared in 0.8.25. Changes with nginx 0.8.27 17 Nov 2009 - *) Bugfix: regular expressions did not work in nginx/Windows; the bug + *) Bugfix: regular expressions did not work in nginx/Windows; the bug had appeared in 0.8.25. Changes with nginx 0.8.26 16 Nov 2009 - *) Bugfix: in captures usage in "rewrite" directive; the bug had + *) Bugfix: in captures usage in "rewrite" directive; the bug had appeared in 0.8.25. - *) Bugfix: nginx could not be built without the --with-debug option; - the bug had appeared in 0.8.25. + *) Bugfix: nginx could not be built without the --with-debug option; the + bug had appeared in 0.8.25. Changes with nginx 0.8.25 16 Nov 2009 - *) Change: now no message is written in an error log if a variable is + *) Change: now no message is written in an error log if a variable is not found by $r->variable() method. *) Feature: the ngx_http_degradation_module. *) Feature: regular expression named captures. - *) Feature: now URI part is not required a "proxy_pass" directive if + *) Feature: now URI part is not required a "proxy_pass" directive if variables are used. *) Feature: now the "msie_padding" directive works for Chrome too. - *) Bugfix: a segmentation fault occurred in a worker process on low + *) Bugfix: a segmentation fault occurred in a worker process on low memory condition; the bug had appeared in 0.8.18. - *) Bugfix: nginx sent gzipped responses to clients those do not support - gzip, if "gzip_static on" and "gzip_vary off"; the bug had appeared + *) Bugfix: nginx sent gzipped responses to clients those do not support + gzip, if "gzip_static on" and "gzip_vary off"; the bug had appeared in 0.8.16. Changes with nginx 0.8.24 11 Nov 2009 - *) Bugfix: nginx always added "Content-Encoding: gzip" response header + *) Bugfix: nginx always added "Content-Encoding: gzip" response header line in 304 responses sent by ngx_http_gzip_static_module. - *) Bugfix: nginx could not be built without the --with-debug option; - the bug had appeared in 0.8.23. - - *) Bugfix: the "unix:" parameter of the "set_real_ip_from" directive + *) Bugfix: nginx could not be built without the --with-debug option; the + bug had appeared in 0.8.23. + + *) Bugfix: the "unix:" parameter of the "set_real_ip_from" directive inherited incorrectly from previous level. *) Bugfix: in resolving empty name. @@ -841,11 +854,11 @@ Changes with nginx 0.8.23 *) Security: now SSL/TLS renegotiation is disabled. Thanks to Maxim Dounin. - *) Bugfix: listen unix domain socket did not inherit while online + *) Bugfix: listen unix domain socket did not inherit while online upgrade. - *) Bugfix: the "unix:" parameter of the "set_real_ip_from" directive - did not without yet another directive with any IP address. + *) Bugfix: the "unix:" parameter of the "set_real_ip_from" directive did + not without yet another directive with any IP address. *) Bugfix: segmentation fault and infinite looping in resolver. @@ -855,17 +868,17 @@ Changes with nginx 0.8.23 Changes with nginx 0.8.22 03 Nov 2009 - *) Feature: the "proxy_bind", "fastcgi_bind", and "memcached_bind" + *) Feature: the "proxy_bind", "fastcgi_bind", and "memcached_bind" directives. *) Feature: the "access" and the "deny" directives support IPv6. - *) Feature: the "set_real_ip_from" directive supports IPv6 addresses in + *) Feature: the "set_real_ip_from" directive supports IPv6 addresses in request headers. *) Feature: the "unix:" parameter of the "set_real_ip_from" directive. - *) Bugfix: nginx did not delete unix domain socket after configuration + *) Bugfix: nginx did not delete unix domain socket after configuration testing. *) Bugfix: nginx deleted unix domain socket while online upgrade. @@ -873,16 +886,16 @@ Changes with nginx 0.8.22 *) Bugfix: the "!-x" operator did not work. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault might occur in a worker process, if + *) Bugfix: a segmentation fault might occur in a worker process, if limit_rate was used in HTTPS server. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault might occur in a worker process while + *) Bugfix: a segmentation fault might occur in a worker process while $limit_rate logging. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault might occur in a worker process, if - there was no "listen" directive in "server" block; the bug had + *) Bugfix: a segmentation fault might occur in a worker process, if + there was no "listen" directive in "server" block; the bug had appeared in 0.8.21. @@ -890,13 +903,13 @@ Changes with nginx 0.8.21 *) Feature: now the "-V" switch shows TLS SNI support. - *) Feature: the "listen" directive of the HTTP module supports unix + *) Feature: the "listen" directive of the HTTP module supports unix domain sockets. Thanks to Hongli Lai. *) Feature: the "default_server" parameter of the "listen" directive. - *) Feature: now a "default" parameter is not required to set listen + *) Feature: now a "default" parameter is not required to set listen socket options. *) Bugfix: nginx did not support dates in 2038 year on 32-bit platforms; @@ -908,22 +921,22 @@ Changes with nginx 0.8.20 *) Change: now default SSL ciphers are "HIGH:!ADH:!MD5". - *) Bugfix: the ngx_http_autoindex_module did not show the trailing - slash in links to a directory; the bug had appeared in 0.7.15. - - *) Bugfix: nginx did not close a log file set by the --error-log-path + *) Bugfix: the ngx_http_autoindex_module did not show the trailing slash + in links to a directory; the bug had appeared in 0.7.15. + + *) Bugfix: nginx did not close a log file set by the --error-log-path configuration option; the bug had appeared in 0.7.53. - *) Bugfix: nginx did not treat a comma as separator in the + *) Bugfix: nginx did not treat a comma as separator in the "Cache-Control" backend response header line. - *) Bugfix: nginx/Windows might not create temporary file, a cache file, - or "proxy/fastcgi_store"d file if a worker had no enough access + *) Bugfix: nginx/Windows might not create temporary file, a cache file, + or "proxy/fastcgi_store"d file if a worker had no enough access rights for top level directories. - *) Bugfix: the "Set-Cookie" and "P3P" FastCGI response header lines - were not hidden while caching if no "fastcgi_hide_header" directives - were used with any parameters. + *) Bugfix: the "Set-Cookie" and "P3P" FastCGI response header lines were + not hidden while caching if no "fastcgi_hide_header" directives were + used with any parameters. *) Bugfix: nginx counted incorrectly disk cache size. @@ -934,8 +947,8 @@ Changes with nginx 0.8.19 *) Change: now default SSL ciphers are "ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM". - *) Bugfix: a "limit_req" directive did not work; the bug had appeared - in 0.8.18. + *) Bugfix: a "limit_req" directive did not work; the bug had appeared in + 0.8.18. Changes with nginx 0.8.18 06 Oct 2009 @@ -944,21 +957,21 @@ Changes with nginx 0.8.18 *) Feature: now several "perl_modules" directives may be used. - *) Feature: the "limit_req_log_level" and "limit_conn_log_level" + *) Feature: the "limit_req_log_level" and "limit_conn_log_level" directives. - *) Bugfix: now "limit_req" directive conforms to the leaky bucket + *) Bugfix: now "limit_req" directive conforms to the leaky bucket algorithm. Thanks to Maxim Dounin. *) Bugfix: nginx did not work on Linux/sparc. Thanks to Marcus Ramberg. - *) Bugfix: nginx sent '\0' in a "Location" response header line on - MKCOL request. + *) Bugfix: nginx sent '\0' in a "Location" response header line on MKCOL + request. Thanks to Xie Zhenye. - *) Bugfix: zero status code was logged instead of 499 status code; the + *) Bugfix: zero status code was logged instead of 499 status code; the bug had appeared in 0.8.11. *) Bugfix: socket leak; the bug had appeared in 0.8.11. @@ -966,7 +979,7 @@ Changes with nginx 0.8.18 Changes with nginx 0.8.17 28 Sep 2009 - *) Security: now "/../" are disabled in "Destination" request header + *) Security: now "/../" are disabled in "Destination" request header line. *) Change: now $host variable value is always low case. @@ -980,7 +993,7 @@ Changes with nginx 0.8.16 *) Feature: the "image_filter_transparency" directive. - *) Bugfix: "addition_types" directive was incorrectly named + *) Bugfix: "addition_types" directive was incorrectly named "addtion_types". *) Bugfix: resolver cache poisoning. @@ -989,31 +1002,31 @@ Changes with nginx 0.8.16 *) Bugfix: memory leak in resolver. Thanks to Matthew Dempsky. - *) Bugfix: invalid request line in $request variable was written in + *) Bugfix: invalid request line in $request variable was written in access_log only if error_log was set to "info" or "debug" level. - *) Bugfix: in PNG alpha-channel support in the + *) Bugfix: in PNG alpha-channel support in the ngx_http_image_filter_module. - *) Bugfix: nginx always added "Vary: Accept-Encoding" response header + *) Bugfix: nginx always added "Vary: Accept-Encoding" response header line, if both "gzip_static" and "gzip_vary" were on. - *) Bugfix: in UTF-8 encoding support by "try_files" directive in + *) Bugfix: in UTF-8 encoding support by "try_files" directive in nginx/Windows. - *) Bugfix: in "post_action" directive usage; the bug had appeared in + *) Bugfix: in "post_action" directive usage; the bug had appeared in 0.8.11. Thanks to Igor Artemiev. Changes with nginx 0.8.15 14 Sep 2009 - *) Security: a segmentation fault might occur in worker process while + *) Security: a segmentation fault might occur in worker process while specially crafted request handling. Thanks to Chris Ries. - *) Bugfix: if names .domain.tld, .sub.domain.tld, and .domain-some.tld - were defined, then the name .sub.domain.tld was matched by + *) Bugfix: if names .domain.tld, .sub.domain.tld, and .domain-some.tld + were defined, then the name .sub.domain.tld was matched by .domain.tld. *) Bugfix: in transparency support in the ngx_http_image_filter_module. @@ -1027,25 +1040,25 @@ Changes with nginx 0.8.15 Changes with nginx 0.8.14 07 Sep 2009 - *) Bugfix: an expired cached response might stick in the "UPDATING" + *) Bugfix: an expired cached response might stick in the "UPDATING" state. - *) Bugfix: a segmentation fault might occur in worker process, if + *) Bugfix: a segmentation fault might occur in worker process, if error_log was set to info or debug level. Thanks to Sergey Bochenkov. *) Bugfix: in embedded perl module; the bug had appeared in 0.8.11. - *) Bugfix: an "error_page" directive did not redirect a 413 error; the + *) Bugfix: an "error_page" directive did not redirect a 413 error; the bug had appeared in 0.6.10. Changes with nginx 0.8.13 31 Aug 2009 - *) Bugfix: in the "aio sendfile" directive; the bug had appeared in + *) Bugfix: in the "aio sendfile" directive; the bug had appeared in 0.8.12. - *) Bugfix: nginx could not be built without the --with-file-aio option + *) Bugfix: nginx could not be built without the --with-file-aio option on FreeBSD; the bug had appeared in 0.8.12. @@ -1060,7 +1073,7 @@ Changes with nginx 0.8.12 Changes with nginx 0.8.11 28 Aug 2009 - *) Change: now directive "gzip_disable msie6" does not disable gzipping + *) Change: now directive "gzip_disable msie6" does not disable gzipping for MSIE 6.0 SV1. *) Feature: file AIO support on FreeBSD and Linux. @@ -1072,35 +1085,34 @@ Changes with nginx 0.8.10 *) Bugfix: memory leaks if GeoIP City database was used. - *) Bugfix: in copying temporary files to permanent storage area; the - bug had appeared in 0.8.9. + *) Bugfix: in copying temporary files to permanent storage area; the bug + had appeared in 0.8.9. Changes with nginx 0.8.9 17 Aug 2009 - *) Feature: now the start cache loader runs in a separate process; this + *) Feature: now the start cache loader runs in a separate process; this should improve large caches handling. - *) Feature: now temporary files and permanent storage area may reside - at different file systems. + *) Feature: now temporary files and permanent storage area may reside at + different file systems. Changes with nginx 0.8.8 10 Aug 2009 *) Bugfix: in handling FastCGI headers split in records. - *) Bugfix: a segmentation fault occurred in worker process, if a - request was handled in two proxied or FastCGIed locations and a - caching was enabled in the first location; the bug had appeared in - 0.8.7. + *) Bugfix: a segmentation fault occurred in worker process, if a request + was handled in two proxied or FastCGIed locations and a caching was + enabled in the first location; the bug had appeared in 0.8.7. Changes with nginx 0.8.7 27 Jul 2009 *) Change: minimum supported OpenSSL version is 0.9.7. - *) Change: the "ask" parameter of the "ssl_verify_client" directive was - changed to the "optional" parameter and now it checks a client + *) Change: the "ask" parameter of the "ssl_verify_client" directive was + changed to the "optional" parameter and now it checks a client certificate if it was offered. Thanks to Brice Figureau. @@ -1112,24 +1124,24 @@ Changes with nginx 0.8.7 *) Feature: the "proxy" parameter of the "geo" directive. - *) Feature: the "image_filter" directive supports variables for setting + *) Feature: the "image_filter" directive supports variables for setting size. - *) Bugfix: the $ssl_client_cert variable usage corrupted memory; the - bug had appeared in 0.7.7. + *) Bugfix: the $ssl_client_cert variable usage corrupted memory; the bug + had appeared in 0.7.7. Thanks to Sergey Zhuravlev. - *) Bugfix: "proxy_pass_header" and "fastcgi_pass_header" directives did - not pass to a client the "X-Accel-Redirect", "X-Accel-Limit-Rate", - "X-Accel-Buffering", and "X-Accel-Charset" lines from backend + *) Bugfix: "proxy_pass_header" and "fastcgi_pass_header" directives did + not pass to a client the "X-Accel-Redirect", "X-Accel-Limit-Rate", + "X-Accel-Buffering", and "X-Accel-Charset" lines from backend response header. Thanks to Maxim Dounin. - *) Bugfix: in handling "Last-Modified" and "Accept-Ranges" backend + *) Bugfix: in handling "Last-Modified" and "Accept-Ranges" backend response header lines; the bug had appeared in 0.7.44. Thanks to Maxim Dounin. - *) Bugfix: the "[alert] zero size buf" error if subrequest returns an + *) Bugfix: the "[alert] zero size buf" error if subrequest returns an empty response; the bug had appeared in 0.8.5. @@ -1137,17 +1149,17 @@ Changes with nginx 0.8.6 *) Feature: the ngx_http_geoip_module. - *) Bugfix: XSLT filter may fail with message "not well formed XML + *) Bugfix: XSLT filter may fail with message "not well formed XML document" for valid XML document. Thanks to Kuramoto Eiji. - *) Bugfix: now in MacOSX, Cygwin, and nginx/Windows locations given by - a regular expression are always tested in case insensitive mode. + *) Bugfix: now in MacOSX, Cygwin, and nginx/Windows locations given by a + regular expression are always tested in case insensitive mode. *) Bugfix: now nginx/Windows ignores trailing dots in URI. Thanks to Hugo Leisink. - *) Bugfix: name of file specified in --conf-path was not honored during + *) Bugfix: name of file specified in --conf-path was not honored during installation; the bug had appeared in 0.6.6. Thanks to Maxim Dounin. @@ -1156,7 +1168,7 @@ Changes with nginx 0.8.5 *) Bugfix: now nginx allows underscores in a request method. - *) Bugfix: a 500 error code was returned for invalid login/password + *) Bugfix: a 500 error code was returned for invalid login/password while HTTP Basic authentication on Windows. *) Bugfix: ngx_http_perl_module responses did not work in subrequests. @@ -1167,7 +1179,7 @@ Changes with nginx 0.8.5 Changes with nginx 0.8.4 22 Jun 2009 - *) Bugfix: nginx could not be built --without-http-cache; the bug had + *) Bugfix: nginx could not be built --without-http-cache; the bug had appeared in 0.8.3. @@ -1177,43 +1189,43 @@ Changes with nginx 0.8.3 *) Bugfix: nginx could not be built on MacOSX 10.6. - *) Bugfix: nginx could not be built --without-http-cache; the bug had + *) Bugfix: nginx could not be built --without-http-cache; the bug had appeared in 0.8.2. - *) Bugfix: a segmentation fault occurred in worker process, if a - backend 401 error was intercepted and the backend did not set the + *) Bugfix: a segmentation fault occurred in worker process, if a backend + 401 error was intercepted and the backend did not set the "WWW-Authenticate" response header line. Thanks to Eugene Mychlo. Changes with nginx 0.8.2 15 Jun 2009 - *) Bugfix: in open_file_cache and proxy/fastcgi cache interaction on + *) Bugfix: in open_file_cache and proxy/fastcgi cache interaction on start up. - *) Bugfix: open_file_cache might cache open file descriptors too long; + *) Bugfix: open_file_cache might cache open file descriptors too long; the bug had appeared in 0.7.4. Changes with nginx 0.8.1 08 Jun 2009 - *) Feature: the "updating" parameter in "proxy_cache_use_stale" and + *) Feature: the "updating" parameter in "proxy_cache_use_stale" and "fastcgi_cache_use_stale" directives. - *) Bugfix: the "If-Modified-Since", "If-Range", etc. client request - header lines were passed to backend while caching if no + *) Bugfix: the "If-Modified-Since", "If-Range", etc. client request + header lines were passed to backend while caching if no "proxy_set_header" directive was used with any parameters. - *) Bugfix: the "Set-Cookie" and "P3P" response header lines were not - hidden while caching if no "proxy_hide_header/fastcgi_hide_header" + *) Bugfix: the "Set-Cookie" and "P3P" response header lines were not + hidden while caching if no "proxy_hide_header/fastcgi_hide_header" directives were used with any parameters. - *) Bugfix: the ngx_http_image_filter_module did not support GIF87a + *) Bugfix: the ngx_http_image_filter_module did not support GIF87a format. Thanks to Denis Ilyinyh. - *) Bugfix: nginx could not be built modules on Solaris 10 and early; - the bug had appeared in 0.7.56. + *) Bugfix: nginx could not be built modules on Solaris 10 and early; the + bug had appeared in 0.7.56. Changes with nginx 0.8.0 02 Jun 2009 @@ -1227,8 +1239,8 @@ Changes with nginx 0.8.0 *) Bugfix: in relative paths handling in nginx/Windows. - *) Bugfix: in proxy_store, fastcgi_store, proxy_cache, and - fastcgi_cache in nginx/Windows. + *) Bugfix: in proxy_store, fastcgi_store, proxy_cache, and fastcgi_cache + in nginx/Windows. *) Bugfix: in memory allocation error handling. Thanks to Maxim Dounin and Kirill A. Korinskiy. @@ -1236,23 +1248,23 @@ Changes with nginx 0.8.0 Changes with nginx 0.7.59 25 May 2009 - *) Feature: the "proxy_cache_methods" and "fastcgi_cache_methods" + *) Feature: the "proxy_cache_methods" and "fastcgi_cache_methods" directives. *) Bugfix: socket leak; the bug had appeared in 0.7.25. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault occurred in worker process, - if a request had no body and the $request_body variable was used; + *) Bugfix: a segmentation fault occurred in worker process, if a request + had no body and the $request_body variable was used; the bug had appeared in 0.7.58. *) Bugfix: the SSL modules might not built on Solaris and Linux; the bug had appeared in 0.7.56. - *) Bugfix: ngx_http_xslt_filter_module responses were not handled by + *) Bugfix: ngx_http_xslt_filter_module responses were not handled by SSI, charset, and gzip filters. - *) Bugfix: a "charset" directive did not set a charset to + *) Bugfix: a "charset" directive did not set a charset to ngx_http_gzip_static_module responses. @@ -1266,24 +1278,24 @@ Changes with nginx 0.7.58 *) Feature: the $request_body variable. - *) Bugfix: in ngx_http_autoindex_module in file name links having a ":" + *) Bugfix: in ngx_http_autoindex_module in file name links having a ":" symbol in the name. - *) Bugfix: "make upgrade" procedure did not work; the bug had appeared + *) Bugfix: "make upgrade" procedure did not work; the bug had appeared in 0.7.53. Thanks to Denis F. Latypoff. Changes with nginx 0.7.57 12 May 2009 - *) Bugfix: a floating-point fault occurred in worker process, if the - ngx_http_image_filter_module errors were redirected to named + *) Bugfix: a floating-point fault occurred in worker process, if the + ngx_http_image_filter_module errors were redirected to named location; the bug had appeared in 0.7.56. Changes with nginx 0.7.56 11 May 2009 - *) Feature: nginx/Windows supports IPv6 in a "listen" directive of the + *) Feature: nginx/Windows supports IPv6 in a "listen" directive of the HTTP module. *) Bugfix: in ngx_http_image_filter_module. @@ -1291,21 +1303,21 @@ Changes with nginx 0.7.56 Changes with nginx 0.7.55 06 May 2009 - *) Bugfix: the http_XXX parameters in "proxy_cache_use_stale" and + *) Bugfix: the http_XXX parameters in "proxy_cache_use_stale" and "fastcgi_cache_use_stale" directives did not work. *) Bugfix: fastcgi cache did not cache header only responses. - *) Bugfix: of "select() failed (9: Bad file descriptor)" error in + *) Bugfix: of "select() failed (9: Bad file descriptor)" error in nginx/Unix and "select() failed (10038: ...)" error in nginx/Windows. - *) Bugfix: a segmentation fault might occur in worker process, if an - "debug_connection" directive was used; the bug had appeared in + *) Bugfix: a segmentation fault might occur in worker process, if an + "debug_connection" directive was used; the bug had appeared in 0.7.54. *) Bugfix: fix ngx_http_image_filter_module building errors. - *) Bugfix: the files bigger than 2G could not be transferred using + *) Bugfix: the files bigger than 2G could not be transferred using $r->sendfile. Thanks to Maxim Dounin. @@ -1314,33 +1326,33 @@ Changes with nginx 0.7.54 *) Feature: the ngx_http_image_filter_module. - *) Feature: the "proxy_ignore_headers" and "fastcgi_ignore_headers" + *) Feature: the "proxy_ignore_headers" and "fastcgi_ignore_headers" directives. - *) Bugfix: a segmentation fault might occur in worker process, if an - "open_file_cache_errors off" directive was used; the bug had - appeared in 0.7.53. - - *) Bugfix: the "port_in_redirect off" directive did not work; the bug + *) Bugfix: a segmentation fault might occur in worker process, if an + "open_file_cache_errors off" directive was used; the bug had appeared + in 0.7.53. + + *) Bugfix: the "port_in_redirect off" directive did not work; the bug had appeared in 0.7.39. *) Bugfix: improve handling of "select" method errors. *) Bugfix: of "select() failed (10022: ...)" error in nginx/Windows. - *) Bugfix: in error text descriptions in nginx/Windows; the bug had + *) Bugfix: in error text descriptions in nginx/Windows; the bug had appeared in 0.7.53. Changes with nginx 0.7.53 27 Apr 2009 - *) Change: now a log set by --error-log-path is created from the very + *) Change: now a log set by --error-log-path is created from the very start-up. - *) Feature: now the start up errors and warnings are outputted to an + *) Feature: now the start up errors and warnings are outputted to an error_log and stderr. - *) Feature: the empty --prefix= configure parameter forces nginx to use + *) Feature: the empty --prefix= configure parameter forces nginx to use a directory where it was run as prefix. *) Feature: the -p switch. @@ -1352,14 +1364,14 @@ Changes with nginx 0.7.53 *) Feature: now switches may be set in condensed form. - *) Bugfix: nginx/Windows did not work if configuration file was given - by the -c switch. - - *) Bugfix: temporary files might be not removed if the "proxy_store", + *) Bugfix: nginx/Windows did not work if configuration file was given by + the -c switch. + + *) Bugfix: temporary files might be not removed if the "proxy_store", "fastcgi_store", "proxy_cache", or "fastcgi_cache" were used. Thanks to Maxim Dounin. - *) Bugfix: an incorrect value was passed to mail proxy authentication + *) Bugfix: an incorrect value was passed to mail proxy authentication server in "Auth-Method" header line; the bug had appeared in 0.7.34. Thanks to Simon Lecaille. @@ -1377,46 +1389,46 @@ Changes with nginx 0.7.52 *) Bugfix: in processing HEAD method while caching. - *) Bugfix: in processing the "If-Modified-Since", "If-Range", etc. + *) Bugfix: in processing the "If-Modified-Since", "If-Range", etc. client request header lines while caching. - *) Bugfix: now the "Set-Cookie" and "P3P" header lines are hidden in + *) Bugfix: now the "Set-Cookie" and "P3P" header lines are hidden in cacheable responses. - *) Bugfix: if nginx was built with the ngx_http_perl_module and with a - perl which supports threads, then during a master process exit the + *) Bugfix: if nginx was built with the ngx_http_perl_module and with a + perl which supports threads, then during a master process exit the message "panic: MUTEX_LOCK" might be issued. - *) Bugfix: nginx could not be built --without-http-cache; the bug had + *) Bugfix: nginx could not be built --without-http-cache; the bug had appeared in 0.7.48. - *) Bugfix: nginx could not be built on platforms different from i386, + *) Bugfix: nginx could not be built on platforms different from i386, amd64, sparc, and ppc; the bug had appeared in 0.7.42. Changes with nginx 0.7.51 12 Apr 2009 - *) Feature: the "try_files" directive supports a response code in the + *) Feature: the "try_files" directive supports a response code in the fallback parameter. *) Feature: now any response code can be used in the "return" directive. - *) Bugfix: the "error_page" directive made an external redirect without + *) Bugfix: the "error_page" directive made an external redirect without query string; the bug had appeared in 0.7.44. - *) Bugfix: if servers listened on several defined explicitly addresses, + *) Bugfix: if servers listened on several defined explicitly addresses, then virtual servers might not work; the bug had appeared in 0.7.39. Changes with nginx 0.7.50 06 Apr 2009 - *) Bugfix: the $arg_... variables did not work; the bug had appeared in + *) Bugfix: the $arg_... variables did not work; the bug had appeared in 0.7.49. Changes with nginx 0.7.49 06 Apr 2009 - *) Bugfix: a segmentation fault might occur in worker process, if the + *) Bugfix: a segmentation fault might occur in worker process, if the $arg_... variables were used; the bug had appeared in 0.7.48. @@ -1424,7 +1436,7 @@ Changes with nginx 0.7.48 *) Feature: the "proxy_cache_key" directive. - *) Bugfix: now nginx takes into account the "X-Accel-Expires", + *) Bugfix: now nginx takes into account the "X-Accel-Expires", "Expires", and "Cache-Control" header lines in a backend response. *) Bugfix: now nginx caches responses for the GET requests only. @@ -1437,28 +1449,28 @@ Changes with nginx 0.7.48 *) Bugfix: nginx could not be built with uclibc library. Thanks to Timothy Redaelli. - *) Bugfix: nginx could not be built on OpenBSD; the bug had + *) Bugfix: nginx could not be built on OpenBSD; the bug had appeared in 0.7.46. Changes with nginx 0.7.47 01 Apr 2009 - *) 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 + *) 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 + *) 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 + *) 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 + *) 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. @@ -1469,30 +1481,29 @@ Changes with nginx 0.7.46 Changes with nginx 0.7.45 30 Mar 2009 - *) Change: now the "proxy_cache" and the "proxy_cache_valid" directives + *) Change: now the "proxy_cache" and the "proxy_cache_valid" directives can be set on different levels. - *) Change: the "clean_time" parameter of the "proxy_cache_path" + *) Change: the "clean_time" parameter of the "proxy_cache_path" directive is canceled. - *) Feature: the "max_size" parameter of the "proxy_cache_path" + *) Feature: the "max_size" parameter of the "proxy_cache_path" directive. *) Feature: the ngx_http_fastcgi_module preliminary cache support. - *) Feature: now on shared memory allocation errors directive and zone + *) Feature: now on shared memory allocation errors directive and zone names are logged. - *) Bugfix: the directive "add_header last-modified ''" did not delete a + *) Bugfix: the directive "add_header last-modified ''" did not delete a "Last-Modified" response header line; the bug had appeared in 0.7.44. - *) Bugfix: a relative path in the "auth_basic_user_file" directive - given without variables did not work; the bug had appeared in - 0.7.44. + *) Bugfix: a relative path in the "auth_basic_user_file" directive given + without variables did not work; the bug had appeared in 0.7.44. Thanks to Jerome Loyet. - *) Bugfix: in an "alias" directive given using variables without - references to captures of regular expressions; the bug had appeared + *) Bugfix: in an "alias" directive given using variables without + references to captures of regular expressions; the bug had appeared in 0.7.42. @@ -1502,86 +1513,85 @@ Changes with nginx 0.7.44 *) Feature: the --with-pcre option in the configure. - *) Feature: the "try_files" directive is now allowed on the server - block level. - - *) Bugfix: the "try_files" directive handled incorrectly a query string + *) Feature: the "try_files" directive is now allowed on the server block + level. + + *) Bugfix: the "try_files" directive handled incorrectly a query string in a fallback parameter. *) Bugfix: the "try_files" directive might test incorrectly directories. - *) Bugfix: if there was a single server for given address:port pair, - then captures in regular expressions in a "server_name" directive - did not work. + *) Bugfix: if there was a single server for given address:port pair, + then captures in regular expressions in a "server_name" directive did + not work. Changes with nginx 0.7.43 18 Mar 2009 - *) Bugfix: a request was handled incorrectly, if a "root" directive - used variables; the bug had appeared in 0.7.42. - - *) Bugfix: if a server listened on wildcard address, then the - $server_addr variable value was "0.0.0.0"; the bug had appeared in + *) Bugfix: a request was handled incorrectly, if a "root" directive used + variables; the bug had appeared in 0.7.42. + + *) Bugfix: if a server listened on wildcard address, then the + $server_addr variable value was "0.0.0.0"; the bug had appeared in 0.7.36. Changes with nginx 0.7.42 16 Mar 2009 - *) Change: now the "Invalid argument" error returned by + *) Change: now the "Invalid argument" error returned by setsockopt(TCP_NODELAY) on Solaris, is ignored. - *) Change: now if a file specified in a "auth_basic_user_file" - directive is absent, then the 403 error is returned instead of the - 500 one. + *) Change: now if a file specified in a "auth_basic_user_file" directive + is absent, then the 403 error is returned instead of the 500 one. *) Feature: the "auth_basic_user_file" directive supports variables. Thanks to Kirill A. Korinskiy. - *) Feature: the "listen" directive supports the "ipv6only" parameter. + *) Feature: the "listen" directive supports the "ipv6only" parameter. Thanks to Zhang Hua. - *) Bugfix: in an "alias" directive with references to captures of + *) Bugfix: in an "alias" directive with references to captures of regular expressions; the bug had appeared in 0.7.40. *) Bugfix: compatibility with Tru64 UNIX. Thanks to Dustin Marquess. - *) Bugfix: nginx could not be built without PCRE library; the bug had + *) Bugfix: nginx could not be built without PCRE library; the bug had appeared in 0.7.41. Changes with nginx 0.7.41 11 Mar 2009 - *) Bugfix: a segmentation fault might occur in worker process, if a - "server_name" or a "location" directives had captures in regular + *) Bugfix: a segmentation fault might occur in worker process, if a + "server_name" or a "location" directives had captures in regular expressions; the issue had appeared in 0.7.40. Thanks to Vladimir Sopot. Changes with nginx 0.7.40 09 Mar 2009 - *) Feature: the "location" directive supports captures in regular + *) Feature: the "location" directive supports captures in regular expressions. - *) Feature: an "alias" directive with capture references may be used + *) Feature: an "alias" directive with capture references may be used inside a location given by a regular expression with captures. - *) Feature: the "server_name" directive supports captures in regular + *) Feature: the "server_name" directive supports captures in regular expressions. - *) Workaround: the ngx_http_autoindex_module did not show the trailing - slash in directories on XFS filesystem; the issue had appeared in + *) Workaround: the ngx_http_autoindex_module did not show the trailing + slash in directories on XFS filesystem; the issue had appeared in 0.7.15. Thanks to Dmitry Kuzmenko. Changes with nginx 0.7.39 02 Mar 2009 - *) Bugfix: large response with SSI might hang, if gzipping was enabled; + *) Bugfix: large response with SSI might hang, if gzipping was enabled; the bug had appeared in 0.7.28. Thanks to Artem Bokhan. - *) Bugfix: a segmentation fault might occur in worker process, if short + *) Bugfix: a segmentation fault might occur in worker process, if short static variants are used in a "try_files" directive. @@ -1589,41 +1599,41 @@ Changes with nginx 0.7.38 *) Feature: authentication failures logging. - *) Bugfix: name/password in auth_basic_user_file were ignored after odd + *) Bugfix: name/password in auth_basic_user_file were ignored after odd number of empty lines. Thanks to Alexander Zagrebin. - *) Bugfix: a segmentation fault occurred in a master process, if long + *) Bugfix: a segmentation fault occurred in a master process, if long path was used in unix domain socket; the bug had appeared in 0.7.36. Changes with nginx 0.7.37 21 Feb 2009 - *) Bugfix: directives using upstreams did not work; the bug had - appeared in 0.7.36. + *) Bugfix: directives using upstreams did not work; the bug had appeared + in 0.7.36. Changes with nginx 0.7.36 21 Feb 2009 - *) Feature: a preliminary IPv6 support; the "listen" directive of the + *) Feature: a preliminary IPv6 support; the "listen" directive of the HTTP module supports IPv6. - *) Bugfix: the $ancient_browser variable did not work for browsers + *) Bugfix: the $ancient_browser variable did not work for browsers preset by a "modern_browser" directives. Changes with nginx 0.7.35 16 Feb 2009 - *) Bugfix: a "ssl_engine" directive did not use a SSL-accelerator for + *) Bugfix: a "ssl_engine" directive did not use a SSL-accelerator for asymmetric ciphers. Thanks to Marcin Gozdalik. - *) Bugfix: a "try_files" directive set MIME type depending on an + *) Bugfix: a "try_files" directive set MIME type depending on an original request extension. - *) Bugfix: "*domain.tld" names were handled incorrectly in - "server_name", "valid_referers", and "map" directives, if - ".domain.tld" and ".subdomain.domain.tld" wildcards were used; + *) Bugfix: "*domain.tld" names were handled incorrectly in + "server_name", "valid_referers", and "map" directives, if + ".domain.tld" and ".subdomain.domain.tld" wildcards were used; the bug had appeared in 0.7.9. @@ -1631,15 +1641,15 @@ Changes with nginx 0.7.34 *) Feature: the "off" parameter of the "if_modified_since" directive. - *) Feature: now nginx sends an HELO/EHLO command after a XCLIENT + *) Feature: now nginx sends an HELO/EHLO command after a XCLIENT command. Thanks to Maxim Dounin. - *) Feature: Microsoft specific "AUTH LOGIN with User Name" mode support + *) Feature: Microsoft specific "AUTH LOGIN with User Name" mode support in mail proxy server. Thanks to Maxim Dounin. - *) Bugfix: in a redirect rewrite directive original arguments were + *) Bugfix: in a redirect rewrite directive original arguments were concatenated with new arguments by a "?" rather than an "&"; the bug had appeared in 0.1.18. Thanks to Maxim Dounin. @@ -1649,35 +1659,34 @@ Changes with nginx 0.7.34 Changes with nginx 0.7.33 02 Feb 2009 - *) Bugfix: a double response might be returned if the epoll or rtsig - methods are used and a redirect was returned to a request with - body. + *) Bugfix: a double response might be returned if the epoll or rtsig + methods are used and a redirect was returned to a request with body. Thanks to Eden Li. - *) Bugfix: the $sent_http_location variable was empty for some - redirects types. - - *) Bugfix: a segmentation fault might occur in worker process if + *) Bugfix: the $sent_http_location variable was empty for some redirects + types. + + *) Bugfix: a segmentation fault might occur in worker process if "resolver" directive was used in SMTP proxy. Changes with nginx 0.7.32 26 Jan 2009 - *) Feature: now a directory existence testing can be set explicitly in + *) Feature: now a directory existence testing can be set explicitly in the "try_files" directive. *) Bugfix: fastcgi_store stored files not always. *) Bugfix: in geo ranges. - *) Bugfix: in shared memory allocations if nginx was built without + *) Bugfix: in shared memory allocations if nginx was built without debugging. Thanks to Andrey Kvasov. Changes with nginx 0.7.31 19 Jan 2009 - *) Change: now the "try_files" directive tests files only and ignores + *) Change: now the "try_files" directive tests files only and ignores directories. *) Feature: the "fastcgi_split_path_info" directive. @@ -1686,35 +1695,34 @@ Changes with nginx 0.7.31 *) Bugfixes in geo ranges. - *) Bugfix: in a miss case ngx_http_memcached_module returned the "END" - line as response body instead of default 404 page body; the bug had + *) Bugfix: in a miss case ngx_http_memcached_module returned the "END" + line as response body instead of default 404 page body; the bug had appeared in 0.7.18. Thanks to Maxim Dounin. - *) Bugfix: while SMTP proxying nginx issued message "250 2.0.0 OK" + *) Bugfix: while SMTP proxying nginx issued message "250 2.0.0 OK" instead of "235 2.0.0 OK"; the bug had appeared in 0.7.22. Thanks to Maxim Dounin. Changes with nginx 0.7.30 24 Dec 2008 - *) Bugfix: a segmentation fault occurred in worker process, if - variables were used in the "fastcgi_pass" or "proxy_pass" directives - and host name must be resolved; the bug had appeared in 0.7.29. + *) Bugfix: a segmentation fault occurred in worker process, if variables + were used in the "fastcgi_pass" or "proxy_pass" directives and host + name must be resolved; the bug had appeared in 0.7.29. Changes with nginx 0.7.29 24 Dec 2008 - *) Bugfix: the "fastcgi_pass" and "proxy_pass" directives did not + *) Bugfix: the "fastcgi_pass" and "proxy_pass" directives did not support variables if unix domain sockets were used. *) Bugfixes in subrequest processing; the bugs had appeared in 0.7.25. - *) Bugfix: a "100 Continue" response was issued for HTTP/1.0 - requests; + *) Bugfix: a "100 Continue" response was issued for HTTP/1.0 requests; Thanks to Maxim Dounin. - *) Bugfix: in memory allocation in the ngx_http_gzip_filter_module on + *) Bugfix: in memory allocation in the ngx_http_gzip_filter_module on Cygwin. @@ -1722,8 +1730,8 @@ Changes with nginx 0.7.28 *) Change: in memory allocation in the ngx_http_gzip_filter_module. - *) Change: the default "gzip_buffers" directive values have been - changed to 32 4k or 16 8k from 4 4k/8k. + *) Change: the default "gzip_buffers" directive values have been changed + to 32 4k or 16 8k from 4 4k/8k. Changes with nginx 0.7.27 15 Dec 2008 @@ -1732,24 +1740,23 @@ Changes with nginx 0.7.27 *) Feature: variables support in the "fastcgi_pass" directive. - *) Feature: now the $geo variable may get an address from a - variable. + *) Feature: now the $geo variable may get an address from a variable. Thanks to Andrei Nigmatulin. - *) Feature: now a location's modifier may be used without space before + *) Feature: now a location's modifier may be used without space before name. *) Feature: the $upstream_response_length variable. *) Bugfix: now a "add_header" directive does not add an empty value. - *) Bugfix: if zero length static file was requested, then nginx just + *) Bugfix: if zero length static file was requested, then nginx just closed connection; the bug had appeared in 0.7.25. *) Bugfix: a MOVE method could not move file in non-existent directory. - *) Bugfix: a segmentation fault occurred in worker process, if no one - named location was defined in server, but some one was used in an + *) Bugfix: a segmentation fault occurred in worker process, if no one + named location was defined in server, but some one was used in an error_page directive. Thanks to Sergey Bochenkov. @@ -1765,7 +1772,7 @@ Changes with nginx 0.7.25 *) Change: now POSTs without "Content-Length" header line are allowed. - *) Bugfix: now the "limit_req" and "limit_conn" directives log a + *) Bugfix: now the "limit_req" and "limit_conn" directives log a prohibition reason. *) Bugfix: in the "delete" parameter of the "geo" directive. @@ -1775,10 +1782,10 @@ Changes with nginx 0.7.24 *) Feature: the "if_modified_since" directive. - *) Bugfix: nginx did not process a FastCGI server response, if the + *) Bugfix: nginx did not process a FastCGI server response, if the server send too many messages to stderr before response. - *) Bugfix: the "$cookie_..." variables did not work in the SSI and the + *) Bugfix: the "$cookie_..." variables did not work in the SSI and the perl module. @@ -1814,7 +1821,7 @@ Changes with nginx 0.7.21 *) Workaround: compatibility with glibc 2.3. Thanks to Eric Benson and Maxim Dounin. - *) Bugfix: nginx could not run on MacOSX 10.4 and earlier; the bug had + *) Bugfix: nginx could not run on MacOSX 10.4 and earlier; the bug had appeared in 0.7.6. @@ -1824,17 +1831,17 @@ Changes with nginx 0.7.20 *) Feature: the ngx_http_limit_req_module. - *) Bugfix: worker processes might exit on a SIGBUS signal on sparc and + *) Bugfix: worker processes might exit on a SIGBUS signal on sparc and ppc platforms; the bug had appeared in 0.7.3. Thanks to Maxim Dounin. - *) Bugfix: the "proxy_pass http://host/some:uri" directives did not + *) Bugfix: the "proxy_pass http://host/some:uri" directives did not work; the bug had appeared in 0.7.12. - *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" + *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" error. - *) Bugfix: the ngx_http_secure_link_module did not work inside + *) Bugfix: the ngx_http_secure_link_module did not work inside locations, whose names are less than 3 characters. *) Bugfix: $server_addr variable might have no value. @@ -1847,7 +1854,7 @@ Changes with nginx 0.7.19 Changes with nginx 0.7.18 13 Oct 2008 - *) Change: the "underscores_in_headers" directive; now nginx does not + *) Change: the "underscores_in_headers" directive; now nginx does not allows underscores in a client request header line names. *) Feature: the ngx_http_secure_link_module. @@ -1858,13 +1865,13 @@ Changes with nginx 0.7.18 *) Feature: the $realpath_root variable. - *) Feature: the "http_502" and "http_504" parameters of the + *) Feature: the "http_502" and "http_504" parameters of the "proxy_next_upstream" directive. - *) Bugfix: the "http_503" parameter of the "proxy_next_upstream" or + *) Bugfix: the "http_503" parameter of the "proxy_next_upstream" or "fastcgi_next_upstream" directives did not work. - *) Bugfix: nginx might send a "Transfer-Encoding: chunked" header line + *) Bugfix: nginx might send a "Transfer-Encoding: chunked" header line for HEAD requests. *) Bugfix: now accept threshold depends on worker_connections. @@ -1876,19 +1883,19 @@ Changes with nginx 0.7.17 *) Feature: the $pid variable. - *) Bugfix: the "directio" optimization that had appeared in 0.7.15 did + *) Bugfix: the "directio" optimization that had appeared in 0.7.15 did not work with open_file_cache. - *) Bugfix: the "access_log" with variables did not work on Linux; the + *) Bugfix: the "access_log" with variables did not work on Linux; the bug had appeared in 0.7.7. - *) Bugfix: the ngx_http_charset_module did not understand quoted - charset name received from backend. + *) Bugfix: the ngx_http_charset_module did not understand quoted charset + name received from backend. Changes with nginx 0.7.16 08 Sep 2008 - *) Bugfix: nginx could not be built on 64-bit platforms; the bug had + *) Bugfix: nginx could not be built on 64-bit platforms; the bug had appeared in 0.7.15. @@ -1896,31 +1903,31 @@ Changes with nginx 0.7.15 *) Feature: the ngx_http_random_index_module. - *) Feature: the "directio" directive has been optimized for file + *) Feature: the "directio" directive has been optimized for file requests starting from arbitrary position. - *) Feature: the "directio" directive turns off sendfile if it is + *) Feature: the "directio" directive turns off sendfile if it is necessary. - *) Feature: now nginx allows underscores in a client request header - line names. + *) Feature: now nginx allows underscores in a client request header line + names. Changes with nginx 0.7.14 01 Sep 2008 - *) Change: now the ssl_certificate and ssl_certificate_key directives + *) Change: now the ssl_certificate and ssl_certificate_key directives have no default values. *) Feature: the "listen" directive supports the "ssl" parameter. - *) Feature: now nginx takes into account a time zone change while + *) Feature: now nginx takes into account a time zone change while reconfiguration on FreeBSD and Linux. - *) Bugfix: the "listen" directive parameters such as "backlog", - "rcvbuf", etc. were not set, if a default server was not the first + *) Bugfix: the "listen" directive parameters such as "backlog", + "rcvbuf", etc. were not set, if a default server was not the first one. - *) Bugfix: if URI part captured by a "rewrite" directive was used as a + *) Bugfix: if URI part captured by a "rewrite" directive was used as a query string, then the query string was not escaped. *) Bugfix: configuration file validity test improvements. @@ -1928,7 +1935,7 @@ Changes with nginx 0.7.14 Changes with nginx 0.7.13 26 Aug 2008 - *) Bugfix: nginx could not be built on Linux and Solaris; the bug had + *) Bugfix: nginx could not be built on Linux and Solaris; the bug had appeared in 0.7.12. @@ -1938,35 +1945,35 @@ Changes with nginx 0.7.12 *) Feature: the "gzip_disable" directive supports special "msie6" mask. - *) Bugfix: if the "max_fails=0" parameter was used in upstream with + *) Bugfix: if the "max_fails=0" parameter was used in upstream with several servers, then a worker process exited on a SIGFPE signal. Thanks to Maxim Dounin. - *) Bugfix: a request body was dropped while redirection via an + *) Bugfix: a request body was dropped while redirection via an "error_page" directive. - *) Bugfix: a full response was returned for request method HEAD while + *) Bugfix: a full response was returned for request method HEAD while redirection via an "error_page" directive. - *) Bugfix: the $r->header_in() method did not return value of the - "Host", "User-Agent", and "Connection" request header lines; the bug + *) Bugfix: the $r->header_in() method did not return value of the + "Host", "User-Agent", and "Connection" request header lines; the bug had appeared in 0.7.0. Changes with nginx 0.7.11 18 Aug 2008 - *) Change: now ngx_http_charset_module does not work by default with + *) Change: now ngx_http_charset_module does not work by default with text/css MIME type. - *) Feature: now nginx returns the 405 status code for POST method + *) Feature: now nginx returns the 405 status code for POST method requesting a static file only if the file exists. *) Feature: the "proxy_ssl_session_reuse" directive. - *) Bugfix: a "proxy_pass" directive without URI part might use original + *) Bugfix: a "proxy_pass" directive without URI part might use original request after the "X-Accel-Redirect" redirection was used; - *) Bugfix: if a directory has search only rights and the first index + *) Bugfix: if a directory has search only rights and the first index file was absent, then nginx returned the 500 status code. *) Bugfix: in inclusive locations; the bugs had appeared in 0.7.1. @@ -1974,25 +1981,25 @@ Changes with nginx 0.7.11 Changes with nginx 0.7.10 13 Aug 2008 - *) Bugfix: in the "addition_types", "charset_types", "gzip_types", - "ssi_types", "sub_filter_types", and "xslt_types" directives; the + *) Bugfix: in the "addition_types", "charset_types", "gzip_types", + "ssi_types", "sub_filter_types", and "xslt_types" directives; the bugs had appeared in 0.7.9. *) Bugfix: of recursive error_page for 500 status code. - *) Bugfix: now the ngx_http_realip_module sets address not for whole + *) Bugfix: now the ngx_http_realip_module sets address not for whole keepalive connection, but for each request passed via the connection. Changes with nginx 0.7.9 12 Aug 2008 - *) Change: now ngx_http_charset_module works by default with following - MIME types: text/html, text/css, text/xml, text/plain, + *) Change: now ngx_http_charset_module works by default with following + MIME types: text/html, text/css, text/xml, text/plain, text/vnd.wap.wml, application/x-javascript, and application/rss+xml. *) Feature: the "charset_types" and "addition_types" directives. - *) Feature: now the "gzip_types", "ssi_types", and "sub_filter_types" + *) Feature: now the "gzip_types", "ssi_types", and "sub_filter_types" directives use hash. *) Feature: the ngx_cpp_test_module. @@ -2002,15 +2009,15 @@ Changes with nginx 0.7.9 *) Feature: the ngx_http_xslt_module improvements and bug fixing. Thanks to Denis F. Latypoff and Maxim Dounin. - *) Bugfix: the "log_not_found" directive did not work for index files + *) Bugfix: the "log_not_found" directive did not work for index files tests. - *) Bugfix: HTTPS connections might hang, if kqueue, epoll, rtsig, or + *) Bugfix: HTTPS connections might hang, if kqueue, epoll, rtsig, or eventport methods were used; the bug had appeared in 0.7.7. - *) Bugfix: if the "server_name", "valid_referers", and "map" directives - used an "*.domain.tld" wildcard and exact name "domain.tld" was not - set, then the exact name was matched by the wildcard; the bug had + *) Bugfix: if the "server_name", "valid_referers", and "map" directives + used an "*.domain.tld" wildcard and exact name "domain.tld" was not + set, then the exact name was matched by the wildcard; the bug had appeared in 0.3.18. @@ -2023,19 +2030,19 @@ Changes with nginx 0.7.8 *) Feature: Solaris directio support. Thanks to Ivan Debnar. - *) Bugfix: now if FastCGI server sends a "Location" header line without + *) Bugfix: now if FastCGI server sends a "Location" header line without status line, then nginx uses 302 status code. Thanks to Maxim Dounin. Changes with nginx 0.7.7 30 Jul 2008 - *) Change: now the EAGAIN error returned by connect() is not considered + *) Change: now the EAGAIN error returned by connect() is not considered as temporary error. - *) Change: now the $ssl_client_cert variable value is a certificate - with TAB character intended before each line except first one; an - unchanged certificate is available in the $ssl_client_raw_cert + *) Change: now the $ssl_client_cert variable value is a certificate with + TAB character intended before each line except first one; an + unchanged certificate is available in the $ssl_client_raw_cert variable. *) Feature: the "ask" parameter in the "ssl_verify_client" directive. @@ -2048,11 +2055,11 @@ Changes with nginx 0.7.7 *) Feature: MacOSX 10.5 sendfile() support. - *) Bugfix: now in MacOSX and Cygwin locations are tested in case - insensitive mode; however, the compare is provided by single-byte + *) Bugfix: now in MacOSX and Cygwin locations are tested in case + insensitive mode; however, the compare is provided by single-byte locales only. - *) Bugfix: mail proxy SSL connections hanged, if select, poll, or + *) Bugfix: mail proxy SSL connections hanged, if select, poll, or /dev/poll methods were used. *) Bugfix: UTF-8 encoding usage in the ngx_http_autoindex_module. @@ -2060,23 +2067,23 @@ Changes with nginx 0.7.7 Changes with nginx 0.7.6 07 Jul 2008 - *) Bugfix: now if variables are used in the "access_log" directive a + *) Bugfix: now if variables are used in the "access_log" directive a request root existence is always tested. - *) Bugfix: the ngx_http_flv_module did not support several values in a + *) Bugfix: the ngx_http_flv_module did not support several values in a query string. Changes with nginx 0.7.5 01 Jul 2008 - *) Bugfixes in variables support in the "access_log" directive; the - bugs had appeared in 0.7.4. - - *) Bugfix: nginx could not be built --without-http_gzip_module; the bug + *) Bugfixes in variables support in the "access_log" directive; the bugs + had appeared in 0.7.4. + + *) Bugfix: nginx could not be built --without-http_gzip_module; the bug had appeared in 0.7.3. Thanks to Kirill A. Korinskiy. - *) Bugfix: if sub_filter and SSI were used together, then responses + *) Bugfix: if sub_filter and SSI were used together, then responses might were transferred incorrectly. @@ -2095,16 +2102,16 @@ Changes with nginx 0.7.4 Changes with nginx 0.7.3 23 Jun 2008 - *) Change: the "rss" extension MIME type has been changed to + *) Change: the "rss" extension MIME type has been changed to "application/rss+xml". - *) Change: now the "gzip_vary" directive turned on issues a + *) Change: now the "gzip_vary" directive turned on issues a "Vary: Accept-Encoding" header line for uncompressed responses too. - *) Feature: now the "rewrite" directive does a redirect automatically - if the "https://" protocol is used. - - *) Bugfix: the "proxy_pass" directive did not work with the HTTPS + *) Feature: now the "rewrite" directive does a redirect automatically if + the "https://" protocol is used. + + *) Bugfix: the "proxy_pass" directive did not work with the HTTPS protocol; the bug had appeared in 0.6.9. @@ -2117,14 +2124,14 @@ Changes with nginx 0.7.2 *) Feature: the $ssl_client_cert variable. Thanks to Manlio Perillo. - *) Bugfix: after changing URI via a "rewrite" directive nginx did not + *) Bugfix: after changing URI via a "rewrite" directive nginx did not search a new location; the bug had appeared in 0.7.1. Thanks to Maxim Dounin. - *) Bugfix: nginx could not be built without PCRE library; the bug had + *) Bugfix: nginx could not be built without PCRE library; the bug had appeared in 0.7.1. - *) Bugfix: when a request to a directory was redirected with the slash + *) Bugfix: when a request to a directory was redirected with the slash added, nginx dropped a query string from the original request. @@ -2132,16 +2139,16 @@ Changes with nginx 0.7.1 *) Change: now locations are searched in a tree. - *) Change: the "optimize_server_names" directive was canceled due to - the "server_name_in_redirect" directive introduction. + *) Change: the "optimize_server_names" directive was canceled due to the + "server_name_in_redirect" directive introduction. *) Change: some long deprecated directives are not supported anymore. - *) Change: the "none" parameter in the "ssl_session_cache" directive; + *) Change: the "none" parameter in the "ssl_session_cache" directive; now this is default parameter. Thanks to Rob Mueller. - *) Bugfix: worker processes might not catch reconfiguration and log + *) Bugfix: worker processes might not catch reconfiguration and log rotation signals. *) Bugfix: nginx could not be built on latest Fedora 9 Linux. @@ -2150,15 +2157,15 @@ Changes with nginx 0.7.1 Changes with nginx 0.7.0 19 May 2008 - *) Change: now the 0x00-0x1F, '"' and '\' characters are escaped as - \xXX in an access_log. + *) Change: now the 0x00-0x1F, '"' and '\' characters are escaped as \xXX + in an access_log. Thanks to Maxim Dounin. *) Change: now nginx allows several "Host" request header line. *) Feature: the "modified" flag in the "expires" directive. - *) Feature: the $uid_got and $uid_set variables may be used at any + *) Feature: the $uid_got and $uid_set variables may be used at any request processing stage. *) Feature: the $hostname variable. @@ -2167,40 +2174,40 @@ Changes with nginx 0.7.0 *) Feature: DESTDIR support. Thanks to Todd A. Fisher and Andras Voroskoi. - *) Bugfix: a segmentation fault might occur in worker process on Linux, + *) Bugfix: a segmentation fault might occur in worker process on Linux, if keepalive was enabled. Changes with nginx 0.6.31 12 May 2008 - *) Bugfix: nginx did not process FastCGI response if header was at the + *) Bugfix: nginx did not process FastCGI response if header was at the end of FastCGI record; the bug had appeared in 0.6.2. Thanks to Sergey Serov. - *) Bugfix: a segmentation fault might occur in worker process if a file + *) Bugfix: a segmentation fault might occur in worker process if a file was deleted and the "open_file_cache_errors" directive was off. Changes with nginx 0.6.30 29 Apr 2008 - *) Change: now if an "include" directive pattern does not match any + *) Change: now if an "include" directive pattern does not match any file, then nginx does not issue an error. - *) Feature: now the time in directives may be specified without spaces, + *) Feature: now the time in directives may be specified without spaces, for example, "1h50m". *) Bugfix: memory leaks if the "ssl_verify_client" directive was on. Thanks to Chavelle Vincent. - *) Bugfix: the "sub_filter" directive might set text to change into + *) Bugfix: the "sub_filter" directive might set text to change into output. - *) Bugfix: the "error_page" directive did not take into account + *) Bugfix: the "error_page" directive did not take into account arguments in redirected URI. *) Bugfix: now nginx always opens files in binary mode under Cygwin. - *) Bugfix: nginx could not be built on OpenBSD; the bug had appeared in + *) Bugfix: nginx could not be built on OpenBSD; the bug had appeared in 0.6.15. @@ -2208,61 +2215,61 @@ Changes with nginx 0.6.29 *) Feature: the ngx_google_perftools_module. - *) Bugfix: the ngx_http_perl_module could not be built on 64-bit + *) Bugfix: the ngx_http_perl_module could not be built on 64-bit platforms; the bug had appeared in 0.6.27. Changes with nginx 0.6.28 13 Mar 2008 - *) Bugfix: the rtsig method could not be built; the bug had appeared in + *) Bugfix: the rtsig method could not be built; the bug had appeared in 0.6.27. Changes with nginx 0.6.27 12 Mar 2008 - *) Change: now by default the rtsig method is not built on + *) Change: now by default the rtsig method is not built on Linux 2.6.18+. - *) Change: now a request method is not changed while redirection to a + *) Change: now a request method is not changed while redirection to a named location via an "error_page" directive. - *) Feature: the "resolver" and "resolver_timeout" directives in SMTP + *) Feature: the "resolver" and "resolver_timeout" directives in SMTP proxy. *) Feature: the "post_action" directive supports named locations. - *) Bugfix: a segmentation fault occurred in worker process, if a - request was redirected from proxy, FastCGI, or memcached location to - static named locations. - - *) Bugfix: browsers did not repeat SSL handshake if there is no valid - client certificate in first handshake. + *) Bugfix: a segmentation fault occurred in worker process, if a request + was redirected from proxy, FastCGI, or memcached location to static + named locations. + + *) Bugfix: browsers did not repeat SSL handshake if there is no valid + client certificate in first handshake. Thanks to Alexander V. Inyukhin. - *) Bugfix: if response code 495-497 was redirected via an "error_page" - directive without code change, then nginx tried to allocate too many + *) Bugfix: if response code 495-497 was redirected via an "error_page" + directive without code change, then nginx tried to allocate too many memory. *) Bugfix: memory leak in long-lived non buffered connections. *) Bugfix: memory leak in resolver. - *) Bugfix: a segmentation fault occurred in worker process, if a - request was redirected from proxy, FastCGI, or memcached location to - static named locations. + *) Bugfix: a segmentation fault occurred in worker process, if a request + was redirected from proxy, FastCGI, or memcached location to static + named locations. *) Bugfix: in the $proxy_host and $proxy_port variables caching. Thanks to Sergey Bochenkov. - *) Bugfix: a "proxy_pass" directive with variables used incorrectly the - same port as in another "proxy_pass" directive with the same host + *) Bugfix: a "proxy_pass" directive with variables used incorrectly the + same port as in another "proxy_pass" directive with the same host name and without variables. Thanks to Sergey Bochenkov. - *) Bugfix: an alert "sendmsg() failed (9: Bad file descriptor)" on some + *) Bugfix: an alert "sendmsg() failed (9: Bad file descriptor)" on some 64-bit platforms while reconfiguration. - *) Bugfix: a segmentation fault occurred in worker process, if empty + *) Bugfix: a segmentation fault occurred in worker process, if empty stub block was used second time in SSI. *) Bugfix: in copying URI part contained escaped symbols into arguments. @@ -2270,69 +2277,69 @@ Changes with nginx 0.6.27 Changes with nginx 0.6.26 11 Feb 2008 - *) Bugfix: the "proxy_store" and "fastcgi_store" directives did not + *) Bugfix: the "proxy_store" and "fastcgi_store" directives did not check a response length. - *) Bugfix: a segmentation fault occurred in worker process, if big - value was used in a "expires" directive. + *) Bugfix: a segmentation fault occurred in worker process, if big value + was used in a "expires" directive. Thanks to Joaquin Cuenca Abela. *) Bugfix: nginx incorrectly detected cache line size on Pentium 4. Thanks to Gena Makhomed. - *) Bugfix: in proxied or FastCGI subrequests a client original method + *) Bugfix: in proxied or FastCGI subrequests a client original method was used instead of the GET method. *) Bugfix: socket leak in HTTPS mode if deferred accept was used. Thanks to Ben Maurer. - *) Bugfix: nginx issued the bogus error message "SSL_shutdown() failed + *) Bugfix: nginx issued the bogus error message "SSL_shutdown() failed (SSL: )"; the bug had appeared in 0.6.23. - *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" + *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" error; the bug had appeared in 0.6.23. Changes with nginx 0.6.25 08 Jan 2008 - *) Change: now the "server_name_in_redirect" directive is used instead + *) Change: now the "server_name_in_redirect" directive is used instead of the "server_name" directive's special "*" parameter. - *) Change: now wildcard and regex names can be used as main name in a + *) Change: now wildcard and regex names can be used as main name in a "server_name" directive. - *) Change: the "satisfy_any" directive was replaced by the "satisfy" + *) Change: the "satisfy_any" directive was replaced by the "satisfy" directive. - *) Workaround: old worker processes might hog CPU after reconfiguration + *) Workaround: old worker processes might hog CPU after reconfiguration if they was run under Linux OpenVZ. *) Feature: the "min_delete_depth" directive. *) Bugfix: the COPY and MOVE methods did not work with single files. - *) Bugfix: the ngx_http_gzip_static_module did not allow the + *) Bugfix: the ngx_http_gzip_static_module did not allow the ngx_http_dav_module to work; the bug had appeared in 0.6.23. *) Bugfix: socket leak in HTTPS mode if deferred accept was used. Thanks to Ben Maurer. - *) Bugfix: nginx could not be built without PCRE library; the bug had + *) Bugfix: nginx could not be built without PCRE library; the bug had appeared in 0.6.23. Changes with nginx 0.6.24 27 Dec 2007 - *) Bugfix: a segmentation fault might occur in worker process if HTTPS + *) Bugfix: a segmentation fault might occur in worker process if HTTPS was used; the bug had appeared in 0.6.23. Changes with nginx 0.6.23 27 Dec 2007 - *) Change: the "off" parameter in the "ssl_session_cache" directive; - now this is default parameter. - - *) Change: the "open_file_cache_retest" directive was renamed to the + *) Change: the "off" parameter in the "ssl_session_cache" directive; now + this is default parameter. + + *) Change: the "open_file_cache_retest" directive was renamed to the "open_file_cache_valid". *) Feature: the "open_file_cache_min_uses" directive. @@ -2341,20 +2348,20 @@ Changes with nginx 0.6.23 *) Feature: the "gzip_disable" directive. - *) Feature: the "memcached_pass" directive may be used inside the "if" + *) Feature: the "memcached_pass" directive may be used inside the "if" block. - *) Bugfix: a segmentation fault occurred in worker process, if the + *) Bugfix: a segmentation fault occurred in worker process, if the "memcached_pass" and "if" directives were used in the same location. - *) Bugfix: if a "satisfy_any on" directive was used and not all access - and auth modules directives were set, then other given access and + *) Bugfix: if a "satisfy_any on" directive was used and not all access + and auth modules directives were set, then other given access and auth directives were not tested; - *) Bugfix: regex parameters in a "valid_referers" directive were not + *) Bugfix: regex parameters in a "valid_referers" directive were not inherited from previous level. - *) Bugfix: a "post_action" directive did run if a request was completed + *) Bugfix: a "post_action" directive did run if a request was completed with 499 status code. *) Bugfix: optimization of 16K buffer usage in a SSL connection. @@ -2363,71 +2370,71 @@ Changes with nginx 0.6.23 *) Bugfix: the STARTTLS in SMTP mode did not work. Thanks to Oleg Motienko. - *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" + *) Bugfix: in HTTPS mode requests might fail with the "bad write retry" error; the bug had appeared in 0.5.13. Changes with nginx 0.6.22 19 Dec 2007 - *) Change: now all ngx_http_perl_module methods return values copied to + *) Change: now all ngx_http_perl_module methods return values copied to perl's allocated memory. - *) Bugfix: if nginx was built with ngx_http_perl_module, the perl - before 5.8.6 was used, and perl supported threads, then during - reconfiguration the master process aborted; the bug had appeared in + *) Bugfix: if nginx was built with ngx_http_perl_module, the perl before + 5.8.6 was used, and perl supported threads, then during + reconfiguration the master process aborted; the bug had appeared in 0.5.9. Thanks to Boris Zhmurov. - *) Bugfix: the ngx_http_perl_module methods may get invalid values of + *) Bugfix: the ngx_http_perl_module methods may get invalid values of the regex captures. - *) Bugfix: a segmentation fault occurred in worker process, if the - $r->has_request_body() method was called for a request whose small + *) Bugfix: a segmentation fault occurred in worker process, if the + $r->has_request_body() method was called for a request whose small request body was already received. - *) Bugfix: large_client_header_buffers did not freed before going to + *) Bugfix: large_client_header_buffers did not freed before going to keep-alive state. Thanks to Olexander Shtepa. - *) Bugfix: the last address was missed in the $upstream_addr variable; + *) Bugfix: the last address was missed in the $upstream_addr variable; the bug had appeared in 0.6.18. - *) Bugfix: the "fastcgi_catch_stderr" directive did return error code; - now it returns 502 code, that can be rerouted to a next server using + *) Bugfix: the "fastcgi_catch_stderr" directive did return error code; + now it returns 502 code, that can be rerouted to a next server using the "fastcgi_next_upstream invalid_header" directive. - *) Bugfix: a segmentation fault occurred in master process if the - "fastcgi_catch_stderr" directive was used; the bug had appeared in + *) Bugfix: a segmentation fault occurred in master process if the + "fastcgi_catch_stderr" directive was used; the bug had appeared in 0.6.10. Thanks to Manlio Perillo. Changes with nginx 0.6.21 03 Dec 2007 - *) Change: if variable values used in a "proxy_pass" directive contain + *) Change: if variable values used in a "proxy_pass" directive contain IP-addresses only, then a "resolver" directive is not mandatory. - *) Bugfix: a segmentation fault might occur in worker process if a - "proxy_pass" directive with URI-part was used; the bug had appeared + *) Bugfix: a segmentation fault might occur in worker process if a + "proxy_pass" directive with URI-part was used; the bug had appeared in 0.6.19. - *) Bugfix: if resolver was used on platform that does not support + *) Bugfix: if resolver was used on platform that does not support kqueue, then nginx issued an alert "name is out of response". Thanks to Andrei Nigmatulin. - *) Bugfix: if the $server_protocol was used in FastCGI parameters and a - request line length was near to the "client_header_buffer_size" - directive value, then nginx issued an alert "fastcgi: the request + *) Bugfix: if the $server_protocol was used in FastCGI parameters and a + request line length was near to the "client_header_buffer_size" + directive value, then nginx issued an alert "fastcgi: the request record is too big". - *) Bugfix: if a plain text HTTP/0.9 version request was made to HTTPS + *) Bugfix: if a plain text HTTP/0.9 version request was made to HTTPS server, then nginx returned usual response. Changes with nginx 0.6.20 28 Nov 2007 - *) Bugfix: a segmentation fault might occur in worker process if a - "proxy_pass" directive with URI-part was used; the bug had appeared + *) Bugfix: a segmentation fault might occur in worker process if a + "proxy_pass" directive with URI-part was used; the bug had appeared in 0.6.19. @@ -2438,20 +2445,20 @@ Changes with nginx 0.6.19 Changes with nginx 0.6.18 27 Nov 2007 - *) Change: now the ngx_http_userid_module adds start time microseconds + *) Change: now the ngx_http_userid_module adds start time microseconds to the cookie field contains a pid value. - *) Change: now the full request line instead of URI only is written to + *) Change: now the full request line instead of URI only is written to error_log. *) Feature: variables support in the "proxy_pass" directive. *) Feature: the "resolver" and "resolver_timeout" directives. - *) Feature: now the directive "add_header last-modified ''" deletes a + *) Feature: now the directive "add_header last-modified ''" deletes a "Last-Modified" response header line. - *) Bugfix: the "limit_rate" directive did not allow to use full + *) Bugfix: the "limit_rate" directive did not allow to use full throughput, even if limit value was very high. @@ -2460,19 +2467,19 @@ Changes with nginx 0.6.17 *) Feature: the "If-Range" request header line support. Thanks to Alexander V. Inyukhin. - *) Bugfix: URL double escaping in a redirect of the "msie_refresh" + *) Bugfix: URL double escaping in a redirect of the "msie_refresh" directive; the bug had appeared in 0.6.4. - *) Bugfix: the "autoindex" directive did not work with the "alias /" + *) Bugfix: the "autoindex" directive did not work with the "alias /" directive. - *) Bugfix: a segmentation fault might occur in worker process if + *) Bugfix: a segmentation fault might occur in worker process if subrequests were used. - *) Bugfix: the big responses may be transferred truncated if SSL and + *) Bugfix: the big responses may be transferred truncated if SSL and gzip were used. - *) Bugfix: the $status variable was equal to 0 if a proxied server + *) Bugfix: the $status variable was equal to 0 if a proxied server returned response in HTTP/0.9 version. @@ -2481,8 +2488,8 @@ Changes with nginx 0.6.16 *) Change: now the uname(2) is used on Linux instead of procfs. Thanks to Ilya Novikov. - *) Bugfix: if the "?" character was in a "error_page" directive, then - it was escaped in a proxied request; the bug had appeared in 0.6.11. + *) Bugfix: if the "?" character was in a "error_page" directive, then it + was escaped in a proxied request; the bug had appeared in 0.6.11. *) Bugfix: compatibility with mget. @@ -2500,21 +2507,21 @@ Changes with nginx 0.6.15 *) Bugfix: nginx did not unescape URI in the "include" SSI command. - *) Bugfix: the segmentation fault was occurred on start or while - reconfiguration if variable was used in the "charset" or + *) Bugfix: the segmentation fault was occurred on start or while + reconfiguration if variable was used in the "charset" or "source_charset" directives. - *) Bugfix: nginx returned the 400 response on requests like + *) Bugfix: nginx returned the 400 response on requests like "GET http://www.domain.com HTTP/1.0". Thanks to James Oakley. - *) Bugfix: if request with request body was redirected using the - "error_page" directive, then nginx tried to read the request body + *) Bugfix: if request with request body was redirected using the + "error_page" directive, then nginx tried to read the request body again; the bug had appeared in 0.6.7. - *) Bugfix: a segmentation fault occurred in worker process if no - server_name was explicitly defined for server processing request; - the bug had appeared in 0.6.7. + *) Bugfix: a segmentation fault occurred in worker process if no + server_name was explicitly defined for server processing request; the + bug had appeared in 0.6.7. Changes with nginx 0.6.14 15 Oct 2007 @@ -2523,31 +2530,31 @@ Changes with nginx 0.6.14 *) Feature: the "encoding" parameter in the "echo" SSI command. - *) Feature: the "access_log" directive may be used inside the + *) Feature: the "access_log" directive may be used inside the "limit_except" block. - *) Bugfix: if all upstream servers were failed, then all servers had - got weight the was equal one until servers became alive; the bug had + *) Bugfix: if all upstream servers were failed, then all servers had got + weight the was equal one until servers became alive; the bug had appeared in 0.6.6. - *) Bugfix: a segmentation fault occurred in worker process if - $date_local and $date_gmt were used outside the + *) Bugfix: a segmentation fault occurred in worker process if + $date_local and $date_gmt were used outside the ngx_http_ssi_filter_module. - *) Bugfix: a segmentation fault might occur in worker process if debug + *) Bugfix: a segmentation fault might occur in worker process if debug log was enabled. Thanks to Andrei Nigmatulin. - *) Bugfix: ngx_http_memcached_module did not set + *) Bugfix: ngx_http_memcached_module did not set $upstream_response_time. Thanks to Maxim Dounin. - *) Bugfix: a worker process may got caught in an endless loop, if the + *) Bugfix: a worker process may got caught in an endless loop, if the memcached was used. - *) Bugfix: nginx supported low case only "close" and "keep-alive" - values in the "Connection" request header line; the bug had appeared - in 0.6.11. + *) Bugfix: nginx supported low case only "close" and "keep-alive" values + in the "Connection" request header line; the bug had appeared in + 0.6.11. *) Bugfix: sub_filter did not work with empty substitution. @@ -2556,7 +2563,7 @@ Changes with nginx 0.6.14 Changes with nginx 0.6.13 24 Sep 2007 - *) Bugfix: nginx did not close directory file on HEAD request if + *) Bugfix: nginx did not close directory file on HEAD request if autoindex was used. Thanks to Arkadiusz Patyk. @@ -2565,82 +2572,82 @@ Changes with nginx 0.6.12 *) Change: mail proxy was split on three modules: pop3, imap and smtp. - *) Feature: the --without-mail_pop3_module, --without-mail_imap_module, + *) Feature: the --without-mail_pop3_module, --without-mail_imap_module, and --without-mail_smtp_module configuration parameters. - *) Feature: the "smtp_greeting_delay" and "smtp_client_buffer" + *) Feature: the "smtp_greeting_delay" and "smtp_client_buffer" directives of the ngx_mail_smtp_module. - *) Bugfix: the trailing wildcards did not work; the bug had appeared in + *) Bugfix: the trailing wildcards did not work; the bug had appeared in 0.6.9. - *) Bugfix: nginx could not start on Solaris if the shared PCRE library + *) Bugfix: nginx could not start on Solaris if the shared PCRE library located in non-standard place was used. - *) Bugfix: the "proxy_hide_header" and "fastcgi_hide_header" directives - did not hide response header lines whose name was longer than 32 + *) Bugfix: the "proxy_hide_header" and "fastcgi_hide_header" directives + did not hide response header lines whose name was longer than 32 characters. Thanks to Manlio Perillo. Changes with nginx 0.6.11 11 Sep 2007 - *) Bugfix: active connection counter always increased if mail proxy was + *) Bugfix: active connection counter always increased if mail proxy was used. - *) Bugfix: if backend returned response header only using non-buffered + *) Bugfix: if backend returned response header only using non-buffered proxy, then nginx closed backend connection on timeout. - *) Bugfix: nginx did not support several "Connection" request header + *) Bugfix: nginx did not support several "Connection" request header lines. - *) Bugfix: if the "max_fails" was set for upstream server, then after - first failure server weight was always one; the bug had appeared in + *) Bugfix: if the "max_fails" was set for upstream server, then after + first failure server weight was always one; the bug had appeared in 0.6.6. Changes with nginx 0.6.10 03 Sep 2007 - *) Feature: the "open_file_cache", "open_file_cache_retest", and + *) Feature: the "open_file_cache", "open_file_cache_retest", and "open_file_cache_errors" directives. *) Bugfix: socket leak; the bug had appeared in 0.6.7. - *) Bugfix: a charset set by the "charset" directive was not appended to + *) Bugfix: a charset set by the "charset" directive was not appended to the "Content-Type" header set by $r->send_http_header(). - *) Bugfix: a segmentation fault might occur in worker process if + *) Bugfix: a segmentation fault might occur in worker process if /dev/poll method was used. Changes with nginx 0.6.9 28 Aug 2007 - *) Bugfix: a worker process may got caught in an endless loop, if the + *) Bugfix: a worker process may got caught in an endless loop, if the HTTPS protocol was used; the bug had appeared in 0.6.7. - *) Bugfix: if server listened on two addresses or ports and trailing + *) Bugfix: if server listened on two addresses or ports and trailing wildcard was used, then nginx did not run. - *) Bugfix: the "ip_hash" directive might incorrectly mark servers as + *) Bugfix: the "ip_hash" directive might incorrectly mark servers as down. - *) Bugfix: nginx could not be built on amd64; the bug had appeared in + *) Bugfix: nginx could not be built on amd64; the bug had appeared in 0.6.8. Changes with nginx 0.6.8 20 Aug 2007 - *) Change: now nginx tries to set the "worker_priority", - "worker_rlimit_nofile", "worker_rlimit_core", and + *) Change: now nginx tries to set the "worker_priority", + "worker_rlimit_nofile", "worker_rlimit_core", and "worker_rlimit_sigpending" without super-user privileges. - *) Change: now nginx escapes space and "%" in request to a mail proxy + *) Change: now nginx escapes space and "%" in request to a mail proxy authentication server. *) Change: now nginx escapes "%" in $memcached_key variable. - *) Bugfix: nginx used path relative to configuration prefix for - non-absolute configuration file path specified in the "-c" key; the + *) Bugfix: nginx used path relative to configuration prefix for + non-absolute configuration file path specified in the "-c" key; the bug had appeared in 0.6.6. *) Bugfix: nginx did not work on FreeBSD/sparc64. @@ -2648,45 +2655,45 @@ Changes with nginx 0.6.8 Changes with nginx 0.6.7 15 Aug 2007 - *) Change: now the paths specified in the "include", - "auth_basic_user_file", "perl_modules", "ssl_certificate", - "ssl_certificate_key", and "ssl_client_certificate" directives are - relative to directory of nginx configuration file nginx.conf, but - not to nginx prefix directory. + *) Change: now the paths specified in the "include", + "auth_basic_user_file", "perl_modules", "ssl_certificate", + "ssl_certificate_key", and "ssl_client_certificate" directives are + relative to directory of nginx configuration file nginx.conf, but not + to nginx prefix directory. *) Change: the --sysconfdir=PATH option in configure was canceled. - *) Change: the special make target "upgrade1" was defined for online + *) Change: the special make target "upgrade1" was defined for online upgrade of 0.1.x versions. - *) Feature: the "server_name" and "valid_referers" directives support + *) Feature: the "server_name" and "valid_referers" directives support regular expressions. - *) Feature: the "server" directive in the "upstream" context supports + *) Feature: the "server" directive in the "upstream" context supports the "backup" parameter. - *) Feature: the ngx_http_perl_module supports the + *) Feature: the ngx_http_perl_module supports the $r->discard_request_body. - *) Feature: the "add_header Last-Modified ..." directive changes the + *) Feature: the "add_header Last-Modified ..." directive changes the "Last-Modified" response header line. - *) Bugfix: if a response different than 200 was returned to a request - with body and connection went to the keep-alive state after the + *) Bugfix: if a response different than 200 was returned to a request + with body and connection went to the keep-alive state after the request, then nginx returned 400 for the next request. - *) Bugfix: a segmentation fault occurred in worker process if invalid + *) Bugfix: a segmentation fault occurred in worker process if invalid address was set in the "auth_http" directive. - *) Bugfix: now nginx uses default listen backlog value 511 on all + *) Bugfix: now nginx uses default listen backlog value 511 on all platforms except FreeBSD. Thanks to Jiang Hong. - *) Bugfix: a worker process may got caught in an endless loop, if a - "server" inside "upstream" block was marked as "down"; the bug had + *) Bugfix: a worker process may got caught in an endless loop, if a + "server" inside "upstream" block was marked as "down"; the bug had appeared in 0.6.6. - *) Bugfix: now Solaris sendfilev() is not used to transfer the client + *) Bugfix: now Solaris sendfilev() is not used to transfer the client request body to FastCGI-server via the unix domain socket. @@ -2702,13 +2709,13 @@ Changes with nginx 0.6.6 *) Bugfix: fair big weight upstream balancer. - *) Bugfix: if a client has closed connection to mail proxy then nginx + *) Bugfix: if a client has closed connection to mail proxy then nginx might not close connection to backend. - *) Bugfix: if the same host without specified port was used as backend + *) Bugfix: if the same host without specified port was used as backend for HTTP and HTTPS, then nginx used only one port - 80 or 443. - *) Bugfix: fix building on Solaris/amd64 by Sun Studio 11 and early + *) Bugfix: fix building on Solaris/amd64 by Sun Studio 11 and early versions; the bug had appeared in 0.6.4. @@ -2725,8 +2732,7 @@ Changes with nginx 0.6.5 *) Bugfix: now nginx escapes space in $memcached_key variable. - *) Bugfix: nginx was incorrectly built by Sun Studio on - Solaris/amd64. + *) Bugfix: nginx was incorrectly built by Sun Studio on Solaris/amd64. Thanks to Jiang Hong. *) Bugfix: of minor potential bugs. @@ -2738,13 +2744,13 @@ Changes with nginx 0.6.4 *) Security: the "msie_refresh" directive allowed XSS. Thanks to Maxim Boguk. - *) Change: the "proxy_store" and "fastcgi_store" directives were + *) Change: the "proxy_store" and "fastcgi_store" directives were changed. - *) Feature: the "proxy_store_access" and "fastcgi_store_access" + *) Feature: the "proxy_store_access" and "fastcgi_store_access" directives. - *) Bugfix: nginx did not work on Solaris/sparc64 if it was built by Sun + *) Bugfix: nginx did not work on Solaris/sparc64 if it was built by Sun Studio. Thanks to Andrei Nigmatulin. @@ -2756,79 +2762,79 @@ Changes with nginx 0.6.3 *) Feature: the "proxy_store" and "fastcgi_store" directives. - *) Bugfix: a segmentation fault might occur in worker process if the + *) Bugfix: a segmentation fault might occur in worker process if the "auth_http_header" directive was used. Thanks to Maxim Dounin. - *) Bugfix: a segmentation fault occurred in worker process if the + *) Bugfix: a segmentation fault occurred in worker process if the CRAM-MD5 authentication method was used, but it was not enabled. - *) Bugfix: a segmentation fault might occur in worker process when the + *) Bugfix: a segmentation fault might occur in worker process when the HTTPS protocol was used in the "proxy_pass" directive. - *) Bugfix: a segmentation fault might occur in worker process if the + *) Bugfix: a segmentation fault might occur in worker process if the eventport method was used. - *) Bugfix: the "proxy_ignore_client_abort" and - "fastcgi_ignore_client_abort" directives did not work; the bug had + *) Bugfix: the "proxy_ignore_client_abort" and + "fastcgi_ignore_client_abort" directives did not work; the bug had appeared in 0.5.13. Changes with nginx 0.6.2 09 Jul 2007 - *) Bugfix: if the FastCGI header was split in records, then nginx - passed garbage in the header to a client. + *) Bugfix: if the FastCGI header was split in records, then nginx passed + garbage in the header to a client. Changes with nginx 0.6.1 17 Jun 2007 *) Bugfix: in SSI parsing. - *) Bugfix: if remote SSI subrequest was used, then posterior local file + *) Bugfix: if remote SSI subrequest was used, then posterior local file subrequest might transferred to client in wrong order. - *) Bugfix: large SSI inclusions buffered in temporary files were + *) Bugfix: large SSI inclusions buffered in temporary files were truncated. - *) Bugfix: the perl $$ variable value in ngx_http_perl_module was equal + *) Bugfix: the perl $$ variable value in ngx_http_perl_module was equal to the master process identification number. Changes with nginx 0.6.0 14 Jun 2007 - *) Feature: the "server_name", "map", and "valid_referers" directives + *) Feature: the "server_name", "map", and "valid_referers" directives support the "www.example.*" wildcards. Changes with nginx 0.5.25 11 Jun 2007 - *) Bugfix: nginx could not be built with the - --without-http_rewrite_module parameter; the bug had appeared in + *) Bugfix: nginx could not be built with the + --without-http_rewrite_module parameter; the bug had appeared in 0.5.24. Changes with nginx 0.5.24 06 Jun 2007 - *) Security: the "ssl_verify_client" directive did not work if request + *) Security: the "ssl_verify_client" directive did not work if request was made using HTTP/0.9. - *) Bugfix: a part of response body might be passed uncompressed if gzip + *) Bugfix: a part of response body might be passed uncompressed if gzip was used; the bug had appeared in 0.5.23. Changes with nginx 0.5.23 04 Jun 2007 - *) Feature: the ngx_http_ssl_module supports Server Name Indication TLS + *) Feature: the ngx_http_ssl_module supports Server Name Indication TLS extension. *) Feature: the "fastcgi_catch_stderr" directive. Thanks to Nick S. Grechukh, OWOX project. - *) Bugfix: a segmentation fault occurred in master process if two + *) Bugfix: a segmentation fault occurred in master process if two virtual servers should bind() to the overlapping ports. - *) Bugfix: if nginx was built with ngx_http_perl_module and perl - supported threads, then during second reconfiguration the error + *) Bugfix: if nginx was built with ngx_http_perl_module and perl + supported threads, then during second reconfiguration the error messages "panic: MUTEX_LOCK" and "perl_parse() failed" were issued. *) Bugfix: in the HTTPS protocol in the "proxy_pass" directive. @@ -2836,20 +2842,20 @@ Changes with nginx 0.5.23 Changes with nginx 0.5.22 29 May 2007 - *) Bugfix: a big request body might not be passed to backend; the bug + *) Bugfix: a big request body might not be passed to backend; the bug had appeared in 0.5.21. Changes with nginx 0.5.21 28 May 2007 - *) Bugfix: if server has more than about ten locations, then regex + *) Bugfix: if server has more than about ten locations, then regex locations might be choosen not in that order as they were specified. - *) Bugfix: a worker process may got caught in an endless loop on 64-bit + *) Bugfix: a worker process may got caught in an endless loop on 64-bit platform, if the 33-rd or next in succession backend has failed. Thanks to Anton Povarov. - *) Bugfix: a bus error might occur on Solaris/sparc64 if the PCRE + *) Bugfix: a bus error might occur on Solaris/sparc64 if the PCRE library was used. Thanks to Andrei Nigmatulin. @@ -2860,22 +2866,21 @@ Changes with nginx 0.5.20 *) Feature: the "sendfile_max_chunk" directive. - *) Feature: the "$http_...", "$sent_http_...", and "$upstream_http_..." + *) Feature: the "$http_...", "$sent_http_...", and "$upstream_http_..." variables may be changed using the "set" directive. - *) Bugfix: a segmentation fault might occur in worker process if the - SSI command 'if expr="$var = /"' was used. - - *) Bugfix: trailing boundary of multipart range response was - transferred incorrectly. + *) Bugfix: a segmentation fault might occur in worker process if the SSI + command 'if expr="$var = /"' was used. + + *) Bugfix: trailing boundary of multipart range response was transferred + incorrectly. Thanks to Evan Miller. - *) Bugfix: nginx did not work on Solaris/sparc64 if it was built by Sun + *) Bugfix: nginx did not work on Solaris/sparc64 if it was built by Sun Studio. Thanks to Andrei Nigmatulin. - *) Bugfix: the ngx_http_perl_module could not be built by Solaris - make. + *) Bugfix: the ngx_http_perl_module could not be built by Solaris make. Thanks to Andrei Nigmatulin. @@ -2883,19 +2888,19 @@ Changes with nginx 0.5.19 *) Change: now the $request_time variable has millisecond precision. - *) Change: the method $r->rflush of ngx_http_perl_module was renamed to + *) Change: the method $r->rflush of ngx_http_perl_module was renamed to the $r->flush. *) Feature: the $upstream_addr variable. - *) Feature: the "proxy_headers_hash_max_size" and + *) Feature: the "proxy_headers_hash_max_size" and "proxy_headers_hash_bucket_size" directives. Thanks to Volodymyr Kostyrko. - *) Bugfix: the files more than 2G could not be transferred using + *) Bugfix: the files more than 2G could not be transferred using sendfile and limit_rate on 64-bit platforms. - *) Bugfix: the files more than 2G could not be transferred using + *) Bugfix: the files more than 2G could not be transferred using sendfile on 64-bit Linux. @@ -2905,16 +2910,16 @@ Changes with nginx 0.5.18 *) Feature: the "$upstream_http_..." variables. - *) Feature: now the $upstream_status and $upstream_response_time + *) Feature: now the $upstream_status and $upstream_response_time variables keep data about all upstreams before X-Accel-Redirect. - *) Bugfix: a segmentation fault occurred in master process after first - reconfiguration and receiving any signal if nginx was built with - ngx_http_perl_module and perl did not support multiplicity; the bug + *) Bugfix: a segmentation fault occurred in master process after first + reconfiguration and receiving any signal if nginx was built with + ngx_http_perl_module and perl did not support multiplicity; the bug had appeared in 0.5.9. - *) Bugfix: if perl did not support multiplicity, then after - reconfiguration perl code did not work; the bug had appeared in + *) Bugfix: if perl did not support multiplicity, then after + reconfiguration perl code did not work; the bug had appeared in 0.3.38. @@ -2922,68 +2927,68 @@ Changes with nginx 0.5.17 *) Change: now nginx always returns the 405 status for the TRACE method. - *) Feature: now nginx supports the "include" directive inside the + *) Feature: now nginx supports the "include" directive inside the "types" block. - *) Bugfix: the $document_root variable usage in the "root" and "alias" + *) Bugfix: the $document_root variable usage in the "root" and "alias" directives is disabled: this caused recursive stack overflow. *) Bugfix: in the HTTPS protocol in the "proxy_pass" directive. - *) Bugfix: in some cases non-cachable variables (such as $uri variable) + *) Bugfix: in some cases non-cachable variables (such as $uri variable) returned old cached value. Changes with nginx 0.5.16 26 Mar 2007 - *) Bugfix: the C-class network was not used as hash key in the - "ip_hash" directive. + *) Bugfix: the C-class network was not used as hash key in the "ip_hash" + directive. Thanks to Pavel Yarkovoy. - *) Bugfix: a segmentation fault might occur in worker process if a - charset was set in the "Content-Type" header line and the line has + *) Bugfix: a segmentation fault might occur in worker process if a + charset was set in the "Content-Type" header line and the line has trailing ";"; the bug had appeared in 0.3.50. - *) Bugfix: the "[alert] zero size buf" error when FastCGI server was - used and a request body written in a temporary file was multiple of + *) Bugfix: the "[alert] zero size buf" error when FastCGI server was + used and a request body written in a temporary file was multiple of 32K. - *) Bugfix: nginx could not be built on Solaris without the --with-debug + *) Bugfix: nginx could not be built on Solaris without the --with-debug option; the bug had appeared in 0.5.15. Changes with nginx 0.5.15 19 Mar 2007 - *) Feature: the mail proxy supports authenticated SMTP proxying and the + *) Feature: the mail proxy supports authenticated SMTP proxying and the "smtp_auth", "smtp_capablities", and "xclient" directives. Thanks to Anton Yuzhaninov and Maxim Dounin. - *) Feature: now the keep-alive connections are closed just after + *) Feature: now the keep-alive connections are closed just after receiving the reconfiguration signal. - *) Change: the "imap" and "auth" directives were renamed to the "mail" + *) Change: the "imap" and "auth" directives were renamed to the "mail" and "pop3_auth" directives. - *) Bugfix: a segmentation fault occurred in worker process if the - CRAM-MD5 authentication method was used and the APOP method was + *) Bugfix: a segmentation fault occurred in worker process if the + CRAM-MD5 authentication method was used and the APOP method was disabled. - *) Bugfix: if the "starttls only" directive was used in POP3 protocol, + *) Bugfix: if the "starttls only" directive was used in POP3 protocol, then nginx allowed authentication without switching to the SSL mode. - *) Bugfix: worker processes did not exit after reconfiguration and did + *) Bugfix: worker processes did not exit after reconfiguration and did not rotate logs if the eventport method was used. - *) Bugfix: a worker process may got caught in an endless loop, if the + *) Bugfix: a worker process may got caught in an endless loop, if the "ip_hash" directive was used. - *) Bugfix: now nginx does not log some alerts if eventport or /dev/poll + *) Bugfix: now nginx does not log some alerts if eventport or /dev/poll methods are used. Changes with nginx 0.5.14 23 Feb 2007 - *) Bugfix: nginx ignored superfluous closing "}" in the end of + *) Bugfix: nginx ignored superfluous closing "}" in the end of configuration file. @@ -2991,33 +2996,33 @@ Changes with nginx 0.5.13 *) Feature: the COPY and MOVE methods. - *) Bugfix: the ngx_http_realip_module set garbage for requests passed + *) Bugfix: the ngx_http_realip_module set garbage for requests passed via keep-alive connection. *) Bugfix: nginx did not work on big-endian 64-bit Linux. Thanks to Andrei Nigmatulin. - *) Bugfix: now when IMAP/POP3 proxy receives too long command it closes + *) Bugfix: now when IMAP/POP3 proxy receives too long command it closes the connection right away, but not after timeout. - *) Bugfix: if the "epoll" method was used and a client closed a - connection prematurely, then nginx closed the connection after a - send timeout only. - - *) Bugfix: nginx could not be built on platforms different from i386, + *) Bugfix: if the "epoll" method was used and a client closed a + connection prematurely, then nginx closed the connection after a send + timeout only. + + *) Bugfix: nginx could not be built on platforms different from i386, amd64, sparc, and ppc; the bug had appeared in 0.5.8. Changes with nginx 0.5.12 12 Feb 2007 - *) Bugfix: nginx could not be built on platforms different from i386, + *) Bugfix: nginx could not be built on platforms different from i386, amd64, sparc, and ppc; the bug had appeared in 0.5.8. - *) Bugfix: a segmentation fault might occur in worker process if the - temporary files were used while working with FastCGI server; the bug + *) Bugfix: a segmentation fault might occur in worker process if the + temporary files were used while working with FastCGI server; the bug had appeared in 0.5.8. - *) Bugfix: a segmentation fault might occur in worker process if the + *) Bugfix: a segmentation fault might occur in worker process if the $fastcgi_script_name variable was logged. *) Bugfix: ngx_http_perl_module could not be built on Solaris. @@ -3028,69 +3033,69 @@ Changes with nginx 0.5.11 *) Feature: now configure detects system PCRE library in MacPorts. Thanks to Chris McGrath. - *) Bugfix: the response was incorrect if several ranges were requested; + *) Bugfix: the response was incorrect if several ranges were requested; the bug had appeared in 0.5.6. - *) Bugfix: the "create_full_put_path" directive could not create the + *) Bugfix: the "create_full_put_path" directive could not create the intermediate directories if no "dav_access" directive was set. Thanks to Evan Miller. - *) Bugfix: the "0" response code might be logged in the access_log + *) Bugfix: the "0" response code might be logged in the access_log instead of the "400" and "408" error codes. - *) Bugfix: a segmentation fault might occur in worker process if nginx + *) Bugfix: a segmentation fault might occur in worker process if nginx was built with -O2 optimization. Changes with nginx 0.5.10 26 Jan 2007 - *) Bugfix: while online executable file upgrade the new master process + *) Bugfix: while online executable file upgrade the new master process did not inherit the listening sockets; the bug had appeared in 0.5.9. - *) Bugfix: a segmentation fault might occur in worker process if nginx + *) Bugfix: a segmentation fault might occur in worker process if nginx was built with -O2 optimization; the bug had appeared in 0.5.1. Changes with nginx 0.5.9 25 Jan 2007 - *) Change: now the ngx_http_memcached_module uses the $memcached_key + *) Change: now the ngx_http_memcached_module uses the $memcached_key variable value as a key. *) Feature: the $memcached_key variable. - *) Feature: the "clean" parameter in the "client_body_in_file_only" + *) Feature: the "clean" parameter in the "client_body_in_file_only" directive. *) Feature: the "env" directive. *) Feature: the "sendfile" directive is available inside the "if" block. - *) Feature: now on failure of the writing to access nginx logs a - message to error_log, but not more often than once a minute. - - *) Bugfix: the "access_log off" directive did not always turn off the + *) Feature: now on failure of the writing to access nginx logs a message + to error_log, but not more often than once a minute. + + *) Bugfix: the "access_log off" directive did not always turn off the logging. Changes with nginx 0.5.8 19 Jan 2007 - *) Bugfix: a segmentation fault might occur if + *) Bugfix: a segmentation fault might occur if "client_body_in_file_only on" was used and a request body was small. - *) Bugfix: a segmentation fault occurred if - "client_body_in_file_only on" and "proxy_pass_request_body off" or - "fastcgi_pass_request_body off" directives were used, and nginx + *) Bugfix: a segmentation fault occurred if + "client_body_in_file_only on" and "proxy_pass_request_body off" or + "fastcgi_pass_request_body off" directives were used, and nginx switched to a next upstream. - *) Bugfix: if the "proxy_buffering off" directive was used and a client - connection was non-active, then the connection was closed after send + *) Bugfix: if the "proxy_buffering off" directive was used and a client + connection was non-active, then the connection was closed after send timeout; the bug had appeared in 0.4.7. - *) Bugfix: if the "epoll" method was used and a client closed a - connection prematurely, then nginx closed the connection after a - send timeout only. - - *) Bugfix: the "[alert] zero size buf" error when FastCGI server was + *) Bugfix: if the "epoll" method was used and a client closed a + connection prematurely, then nginx closed the connection after a send + timeout only. + + *) Bugfix: the "[alert] zero size buf" error when FastCGI server was used. *) Bugfixes in the "limit_zone" directive. @@ -3102,15 +3107,15 @@ Changes with nginx 0.5.7 *) Bugfixes in the "ssl_session_cache" and "limit_zone" directives. - *) Bugfix: the segmentation fault was occurred on start or while - reconfiguration if the "ssl_session_cache" or "limit_zone" - directives were used on 64-bit platforms. - - *) Bugfix: a segmentation fault occurred if the "add_before_body" or - "add_after_body" directives were used and there was no - "Content-Type" header line in response. - - *) Bugfix: the OpenSSL library was always built with the threads + *) Bugfix: the segmentation fault was occurred on start or while + reconfiguration if the "ssl_session_cache" or "limit_zone" directives + were used on 64-bit platforms. + + *) Bugfix: a segmentation fault occurred if the "add_before_body" or + "add_after_body" directives were used and there was no "Content-Type" + header line in response. + + *) Bugfix: the OpenSSL library was always built with the threads support. Thanks to Den Ivanov. @@ -3119,19 +3124,19 @@ Changes with nginx 0.5.7 Changes with nginx 0.5.6 09 Jan 2007 - *) Change: now the ngx_http_index_module ignores all methods except the + *) Change: now the ngx_http_index_module ignores all methods except the GET, HEAD, and POST methods. *) Feature: the ngx_http_limit_zone_module. *) Feature: the $binary_remote_addr variable. - *) Feature: the "ssl_session_cache" directives of the + *) Feature: the "ssl_session_cache" directives of the ngx_http_ssl_module and ngx_imap_ssl_module. *) Feature: the DELETE method supports recursive removal. - *) Bugfix: the byte-ranges were transferred incorrectly if the + *) Bugfix: the byte-ranges were transferred incorrectly if the $r->sendfile() was used. @@ -3141,13 +3146,13 @@ Changes with nginx 0.5.5 *) Feature: the -V switch. - *) Feature: the "worker_rlimit_core" directive supports size in K, M, + *) Feature: the "worker_rlimit_core" directive supports size in K, M, and G. - *) Bugfix: the nginx.pm module now could be installed by an - unprivileged user. - - *) Bugfix: a segmentation fault might occur if the $r->request_body or + *) Bugfix: the nginx.pm module now could be installed by an unprivileged + user. + + *) Bugfix: a segmentation fault might occur if the $r->request_body or $r->request_body_file methods were used. *) Bugfix: the ppc platform specific bugs. @@ -3155,85 +3160,85 @@ Changes with nginx 0.5.5 Changes with nginx 0.5.4 15 Dec 2006 - *) Feature: the "perl" directive may be used inside the "limit_except" + *) Feature: the "perl" directive may be used inside the "limit_except" block. - *) Bugfix: the ngx_http_dav_module required the "Date" request header + *) Bugfix: the ngx_http_dav_module required the "Date" request header line for the DELETE method. - *) Bugfix: if one only parameter was used in the "dav_access" - directive, then nginx might report about configuration error. - - *) Bugfix: a segmentation fault might occur if the $host variable was + *) Bugfix: if one only parameter was used in the "dav_access" directive, + then nginx might report about configuration error. + + *) Bugfix: a segmentation fault might occur if the $host variable was used; the bug had appeared in 0.4.14. Changes with nginx 0.5.3 13 Dec 2006 - *) Feature: the ngx_http_perl_module supports the $r->status, + *) Feature: the ngx_http_perl_module supports the $r->status, $r->log_error, and $r->sleep methods. - *) Feature: the $r->variable method supports variables that do not - exist in nginx configuration. + *) Feature: the $r->variable method supports variables that do not exist + in nginx configuration. *) Bugfix: the $r->has_request_body method did not work. Changes with nginx 0.5.2 11 Dec 2006 - *) Bugfix: if the "proxy_pass" directive used the name of the - "upstream" block, then nginx tried to resolve the name; the bug had - appeared in 0.5.1. + *) Bugfix: if the "proxy_pass" directive used the name of the "upstream" + block, then nginx tried to resolve the name; the bug had appeared in + 0.5.1. Changes with nginx 0.5.1 11 Dec 2006 - *) Bugfix: the "post_action" directive might not run after a + *) Bugfix: the "post_action" directive might not run after a unsuccessful completion of a request. *) Workaround: for Eudora for Mac; the bug had appeared in 0.4.11. Thanks to Bron Gondwana. - *) Bugfix: if the "upstream" name was used in the "fastcgi_pass", then - the message "no port in upstream" was issued; the bug had appeared - in 0.5.0. - - *) Bugfix: if the "proxy_pass" and "fastcgi_pass" directives used the - same servers but different ports, then these directives uses the + *) Bugfix: if the "upstream" name was used in the "fastcgi_pass", then + the message "no port in upstream" was issued; the bug had appeared in + 0.5.0. + + *) Bugfix: if the "proxy_pass" and "fastcgi_pass" directives used the + same servers but different ports, then these directives uses the first described port; the bug had appeared in 0.5.0. - *) Bugfix: if the "proxy_pass" and "fastcgi_pass" directives used the - unix domain sockets, then these directives used first described + *) Bugfix: if the "proxy_pass" and "fastcgi_pass" directives used the + unix domain sockets, then these directives used first described socket; the bug had appeared in 0.5.0. - *) Bugfix: ngx_http_auth_basic_module ignored the user if it was in the - last line in the password file and there was no the carriage return, + *) Bugfix: ngx_http_auth_basic_module ignored the user if it was in the + last line in the password file and there was no the carriage return, the line feed, or the ":" symbol after the password. - *) Bugfix: the $upstream_response_time variable might be equal to + *) Bugfix: the $upstream_response_time variable might be equal to "0.000", although response time was more than 1 millisecond. Changes with nginx 0.5.0 04 Dec 2006 - *) Change: the parameters in the "%name" form in the "log_format" + *) Change: the parameters in the "%name" form in the "log_format" directive are not supported anymore. - *) Change: the "proxy_upstream_max_fails", - "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails", - "fastcgi_upstream_fail_timeout", "memcached_upstream_max_fails", and - "memcached_upstream_fail_timeout" directives are not supported + *) Change: the "proxy_upstream_max_fails", + "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails", + "fastcgi_upstream_fail_timeout", "memcached_upstream_max_fails", and + "memcached_upstream_fail_timeout" directives are not supported anymore. - *) Feature: the "server" directive in the "upstream" context supports + *) Feature: the "server" directive in the "upstream" context supports the "max_fails", "fail_timeout", and "down" parameters. *) Feature: the "ip_hash" directive inside the "upstream" block. - *) Feature: the WAIT status in the "Auth-Status" header line of the + *) Feature: the WAIT status in the "Auth-Status" header line of the IMAP/POP3 proxy authentication server response. - *) Bugfix: nginx could not be built on 64-bit platforms; the bug had + *) Bugfix: nginx could not be built on 64-bit platforms; the bug had appeared in 0.4.14. @@ -3241,62 +3246,62 @@ Changes with nginx 0.4.14 *) Feature: the "proxy_pass_error_message" directive in IMAP/POP3 proxy. - *) Feature: now configure detects system PCRE library on FreeBSD, - Linux, and NetBSD. - - *) Bugfix: ngx_http_perl_module did not work with perl built with the + *) Feature: now configure detects system PCRE library on FreeBSD, Linux, + and NetBSD. + + *) Bugfix: ngx_http_perl_module did not work with perl built with the threads support; the bug had appeared in 0.3.38. - *) Bugfix: ngx_http_perl_module did not work if perl was called + *) Bugfix: ngx_http_perl_module did not work if perl was called recursively. *) Bugfix: nginx ignored a host name in a request line. - *) Bugfix: a worker process may got caught in an endless loop, if a + *) Bugfix: a worker process may got caught in an endless loop, if a FastCGI server sent too many data to the stderr. - *) Bugfix: the $upstream_response_time variable may be negative if the + *) Bugfix: the $upstream_response_time variable may be negative if the system time was changed backward. - *) Bugfix: the "Auth-Login-Attempt" parameter was not sent to IMAP/POP3 + *) Bugfix: the "Auth-Login-Attempt" parameter was not sent to IMAP/POP3 proxy authentication server when POP3 was used. - *) Bugfix: a segmentation fault might occur if connect to IMAP/POP3 + *) Bugfix: a segmentation fault might occur if connect to IMAP/POP3 proxy authentication server failed. Changes with nginx 0.4.13 15 Nov 2006 - *) Feature: the "proxy_pass" directive may be used inside the + *) Feature: the "proxy_pass" directive may be used inside the "limit_except" block. *) Feature: the "limit_except" directive supports all WebDAV methods. - *) Bugfix: if the "add_before_body" directive was used without the - "add_after_body" directive, then a response did not transferred + *) Bugfix: if the "add_before_body" directive was used without the + "add_after_body" directive, then a response did not transferred complete. - *) Bugfix: a large request body did not receive if the epoll method and + *) Bugfix: a large request body did not receive if the epoll method and the deferred accept() were used. - *) Bugfix: a charset could not be set for ngx_http_autoindex_module + *) Bugfix: a charset could not be set for ngx_http_autoindex_module responses; the bug had appeared in 0.3.50. - *) Bugfix: the "[alert] zero size buf" error when FastCGI server was + *) Bugfix: the "[alert] zero size buf" error when FastCGI server was used; *) Bugfix: the --group= configuration parameter was ignored. Thanks to Thomas Moschny. - *) Bugfix: the 50th subrequest in SSI response did not work; the bug - had appeared in 0.3.50. + *) Bugfix: the 50th subrequest in SSI response did not work; the bug had + appeared in 0.3.50. Changes with nginx 0.4.12 31 Oct 2006 *) Feature: the ngx_http_perl_module supports the $r->variable method. - *) Bugfix: if a big static file was included using SSI in a response, + *) Bugfix: if a big static file was included using SSI in a response, then the response may be transferred incomplete. *) Bugfix: nginx did not omit the "#fragment" part in URI. @@ -3306,28 +3311,28 @@ Changes with nginx 0.4.11 *) Feature: the POP3 proxy supports the AUTH LOGIN PLAIN and CRAM-MD5. - *) Feature: the ngx_http_perl_module supports the $r->allow_ranges + *) Feature: the ngx_http_perl_module supports the $r->allow_ranges method. - *) Bugfix: if the APOP was enabled in the POP3 proxy, then the - USER/PASS commands might not work; the bug had appeared in 0.4.10. + *) Bugfix: if the APOP was enabled in the POP3 proxy, then the USER/PASS + commands might not work; the bug had appeared in 0.4.10. Changes with nginx 0.4.10 23 Oct 2006 *) Feature: the POP3 proxy supports the APOP command. - *) Bugfix: if the select, poll or /dev/poll methods were used, then - while waiting authentication server response the IMAP/POP3 proxy + *) Bugfix: if the select, poll or /dev/poll methods were used, then + while waiting authentication server response the IMAP/POP3 proxy hogged CPU. - *) Bugfix: a segmentation fault might occur if the $server_addr - variable was used in the "map" directive. - - *) Bugfix: the ngx_http_flv_module did not support the byte ranges for + *) Bugfix: a segmentation fault might occur if the $server_addr variable + was used in the "map" directive. + + *) Bugfix: the ngx_http_flv_module did not support the byte ranges for full responses; the bug had appeared in 0.4.7. - *) Bugfix: nginx could not be built on Debian amd64; the bug had + *) Bugfix: nginx could not be built on Debian amd64; the bug had appeared in 0.4.9. @@ -3335,17 +3340,17 @@ Changes with nginx 0.4.9 *) Feature: the "set" parameter in the "include" SSI command. - *) Feature: the ngx_http_perl_module now tests the nginx.pm module + *) Feature: the ngx_http_perl_module now tests the nginx.pm module version. Changes with nginx 0.4.8 11 Oct 2006 - *) Bugfix: if an "include" SSI command were before another "include" - SSI command with a "wait" parameter, then the "wait" parameter might - not work. - - *) Bugfix: the ngx_http_flv_module added the FLV header to the full + *) Bugfix: if an "include" SSI command were before another "include" SSI + command with a "wait" parameter, then the "wait" parameter might not + work. + + *) Bugfix: the ngx_http_flv_module added the FLV header to the full responses. Thanks to Alexey Kovyrin. @@ -3356,38 +3361,38 @@ Changes with nginx 0.4.7 *) Feature: the $request_body_file variable. - *) Feature: the "charset" and "source_charset" directives support the + *) Feature: the "charset" and "source_charset" directives support the variables. - *) Bugfix: if an "include" SSI command were before another "include" - SSI command with a "wait" parameter, then the "wait" parameter might - not work. - - *) Bugfix: if the "proxy_buffering off" directive was used or while - working with memcached the connections might not be closed on + *) Bugfix: if an "include" SSI command were before another "include" SSI + command with a "wait" parameter, then the "wait" parameter might not + work. + + *) Bugfix: if the "proxy_buffering off" directive was used or while + working with memcached the connections might not be closed on timeout. - *) Bugfix: nginx did not run on 64-bit platforms except amd64, sparc64, + *) Bugfix: nginx did not run on 64-bit platforms except amd64, sparc64, and ppc64. Changes with nginx 0.4.6 06 Oct 2006 - *) Bugfix: nginx did not run on 64-bit platforms except amd64, sparc64, + *) Bugfix: nginx did not run on 64-bit platforms except amd64, sparc64, and ppc64. *) Bugfix: nginx sent the chunked response for HTTP/1.1 request, - if its length was set by text string in the + if its length was set by text string in the $r->headers_out("Content-Length", ...) method. - *) Bugfix: after redirecting error by an "error_page" directive any - ngx_http_rewrite_module directive returned this error code; the bug + *) Bugfix: after redirecting error by an "error_page" directive any + ngx_http_rewrite_module directive returned this error code; the bug had appeared in 0.4.4. Changes with nginx 0.4.5 02 Oct 2006 - *) Bugfix: nginx could not be built on Linux and Solaris; the bug had + *) Bugfix: nginx could not be built on Linux and Solaris; the bug had appeared in 0.4.4. @@ -3400,29 +3405,29 @@ Changes with nginx 0.4.4 *) Feature: the "include" directive supports the "*" mask. Thanks to Jonathan Dance. - *) Bugfix: the "return" directive always overrode the "error_page" + *) Bugfix: the "return" directive always overrode the "error_page" response code redirected by the "error_page" directive. - *) Bugfix: a segmentation fault occurred if zero-length body was in PUT + *) Bugfix: a segmentation fault occurred if zero-length body was in PUT method. - *) Bugfix: the redirect was changed incorrectly if the variables were + *) Bugfix: the redirect was changed incorrectly if the variables were used in the "proxy_redirect" directive. Changes with nginx 0.4.3 26 Sep 2006 - *) Change: now the 499 error could not be redirected using an + *) Change: now the 499 error could not be redirected using an "error_page" directive. *) Feature: the Solaris 10 event ports support. *) Feature: the ngx_http_browser_module. - *) Bugfix: a segmentation fault may occur while redirecting the 400 + *) Bugfix: a segmentation fault may occur while redirecting the 400 error to the proxied server using a "proxy_pass" directive. - *) Bugfix: a segmentation fault occurred if an unix domain socket was + *) Bugfix: a segmentation fault occurred if an unix domain socket was used in a "proxy_pass" directive; the bug had appeared in 0.3.47. *) Bugfix: SSI did work with memcached and nonbuffered responses. @@ -3432,8 +3437,8 @@ Changes with nginx 0.4.3 Changes with nginx 0.4.2 14 Sep 2006 - *) Bugfix: the O_NOATIME flag support on Linux was canceled; the bug - had appeared in 0.4.1. + *) Bugfix: the O_NOATIME flag support on Linux was canceled; the bug had + appeared in 0.4.1. Changes with nginx 0.4.1 14 Sep 2006 @@ -3441,32 +3446,31 @@ Changes with nginx 0.4.1 *) Bugfix: the DragonFlyBSD compatibility. Thanks to Pavel Nazarov. - *) Workaround: of bug in 64-bit Linux sendfile(), when file is more - than 2G. - - *) Feature: now on Linux nginx uses O_NOATIME flag for static - requests. + *) Workaround: of bug in 64-bit Linux sendfile(), when file is more than + 2G. + + *) Feature: now on Linux nginx uses O_NOATIME flag for static requests. Thanks to Yusuf Goolamabbas. Changes with nginx 0.4.0 30 Aug 2006 - *) Change in internal API: the HTTP modules initialization was moved + *) Change in internal API: the HTTP modules initialization was moved from the init module phase to the HTTP postconfiguration phase. - *) Change: now the request body is not read beforehand for the - ngx_http_perl_module: it's required to start the reading using the + *) Change: now the request body is not read beforehand for the + ngx_http_perl_module: it's required to start the reading using the $r->has_request_body method. *) Feature: the ngx_http_perl_module supports the DECLINED return code. - *) Feature: the ngx_http_dav_module supports the incoming "Date" header + *) Feature: the ngx_http_dav_module supports the incoming "Date" header line for the PUT method. *) Feature: the "ssi" directive is available inside the "if" block. - *) Bugfix: a segmentation fault occurred if there was an "index" - directive with variables and the first index name was without + *) Bugfix: a segmentation fault occurred if there was an "index" + directive with variables and the first index name was without variables; the bug had appeared in 0.1.29. @@ -3478,26 +3482,26 @@ Changes with nginx 0.3.61 *) Feature: the "recursive_error_pages" directive. - *) Bugfix: the "rewrite" directive returned incorrect redirect, if the + *) Bugfix: the "rewrite" directive returned incorrect redirect, if the redirect had the captured escaped symbols from original URI. Changes with nginx 0.3.60 18 Aug 2006 - *) Bugfix: a worker process may got caught in an endless loop while an + *) Bugfix: a worker process may got caught in an endless loop while an error redirection; the bug had appeared in 0.3.59. Changes with nginx 0.3.59 16 Aug 2006 - *) Feature: now is possible to do several redirection using the + *) Feature: now is possible to do several redirection using the "error_page" directive. *) Bugfix: the "dav_access" directive did not support three parameters. - *) Bugfix: the "error_page" directive did not changes the - "Content-Type" header line after the "X-Accel-Redirect" was used; - the bug had appeared in 0.3.58. + *) Bugfix: the "error_page" directive did not changes the "Content-Type" + header line after the "X-Accel-Redirect" was used; the bug had + appeared in 0.3.58. Changes with nginx 0.3.58 14 Aug 2006 @@ -3506,12 +3510,12 @@ Changes with nginx 0.3.58 *) Change: now the procfs interface instead of sysctl is used on Linux. - *) Change: now the "Content-Type" header line is inherited from first + *) Change: now the "Content-Type" header line is inherited from first response when the "X-Accel-Redirect" was used. *) Bugfix: the "error_page" directive did not redirect the 413 error. - *) Bugfix: the trailing "?" did not remove old arguments if no new + *) Bugfix: the trailing "?" did not remove old arguments if no new arguments were added to a rewritten URI. *) Bugfix: nginx could not run on 64-bit FreeBSD 7.0-CURRENT. @@ -3524,10 +3528,10 @@ Changes with nginx 0.3.57 *) Bugfix: in the "!-e" operator of the "if" directive. Thanks to Andrian Budanstov. - *) Bugfix: while a client certificate verification nginx did not send - to a client the required certificates information. - - *) Bugfix: the $document_root variable did not support the variables in + *) Bugfix: while a client certificate verification nginx did not send to + a client the required certificates information. + + *) Bugfix: the $document_root variable did not support the variables in the "root" directive. @@ -3535,11 +3539,11 @@ Changes with nginx 0.3.56 *) Feature: the "dav_access" directive. - *) Feature: the "if" directive supports the "-d", "!-d", "-e", "!-e", + *) Feature: the "if" directive supports the "-d", "!-d", "-e", "!-e", "-x", and "!-x" operators. - *) Bugfix: a segmentation fault occurred if a request returned a - redirect and some sent to client header lines were logged in the + *) Bugfix: a segmentation fault occurred if a request returned a + redirect and some sent to client header lines were logged in the access log. @@ -3551,108 +3555,108 @@ Changes with nginx 0.3.55 *) Feature: the unicode2nginx script was added to contrib. - *) Bugfix: if a "root" was specified by variable only, then the root - was relative to a server prefix. - - *) Bugfix: if the request contained "//" or "/./" and escaped symbols + *) Bugfix: if a "root" was specified by variable only, then the root was + relative to a server prefix. + + *) Bugfix: if the request contained "//" or "/./" and escaped symbols after them, then the proxied request was sent unescaped. - *) Bugfix: the $r->header_in("Cookie") of the ngx_http_perl_module now + *) Bugfix: the $r->header_in("Cookie") of the ngx_http_perl_module now returns all "Cookie" header lines. - *) Bugfix: a segmentation fault occurred if - "client_body_in_file_only on" was used and nginx switched to a next + *) Bugfix: a segmentation fault occurred if + "client_body_in_file_only on" was used and nginx switched to a next upstream. - *) Bugfix: on some condition while reconfiguration character codes - inside the "charset_map" may be treated invalid; the bug had - appeared in 0.3.50. + *) Bugfix: on some condition while reconfiguration character codes + inside the "charset_map" may be treated invalid; the bug had appeared + in 0.3.50. Changes with nginx 0.3.54 11 Jul 2006 *) Feature: nginx now logs the subrequest information to the error log. - *) Feature: the "proxy_next_upstream", "fastcgi_next_upstream", and + *) Feature: the "proxy_next_upstream", "fastcgi_next_upstream", and "memcached_next_upstream" directives support the "off" parameter. - *) Feature: the "debug_connection" directive supports the CIDR address + *) Feature: the "debug_connection" directive supports the CIDR address form. - *) Bugfix: if a response of proxied server or FastCGI server was + *) Bugfix: if a response of proxied server or FastCGI server was converted from UTF-8 or back, then it may be transferred incomplete. - *) Bugfix: the $upstream_response_time variable had the time of the + *) Bugfix: the $upstream_response_time variable had the time of the first request to a backend only. - *) Bugfix: nginx could not be built on amd64 platform; the bug had + *) Bugfix: nginx could not be built on amd64 platform; the bug had appeared in 0.3.53. Changes with nginx 0.3.53 07 Jul 2006 - *) Change: the "add_header" directive adds the string to 204, 301, and + *) Change: the "add_header" directive adds the string to 204, 301, and 302 responses. - *) Feature: the "server" directive in the "upstream" context supports + *) Feature: the "server" directive in the "upstream" context supports the "weight" parameter. *) Feature: the "server_name" directive supports the "*" wildcard. *) Feature: nginx supports the request body size more than 2G. - *) Bugfix: if a client was successfully authorized using "satisfy_any - on", then anyway the message "access forbidden by rule" was written + *) Bugfix: if a client was successfully authorized using "satisfy_any + on", then anyway the message "access forbidden by rule" was written in the log. - *) Bugfix: the "PUT" method may erroneously not create a file and - return the 409 code. - - *) Bugfix: if the IMAP/POP3 backend returned an error, then nginx + *) Bugfix: the "PUT" method may erroneously not create a file and return + the 409 code. + + *) Bugfix: if the IMAP/POP3 backend returned an error, then nginx continued proxying anyway. Changes with nginx 0.3.52 03 Jul 2006 - *) Change: the ngx_http_index_module behavior for the "POST /" requests - is reverted to the 0.3.40 version state: the module now does not + *) Change: the ngx_http_index_module behavior for the "POST /" requests + is reverted to the 0.3.40 version state: the module now does not return the 405 error. - *) Bugfix: the worker process may got caught in an endless loop if the + *) Bugfix: the worker process may got caught in an endless loop if the limit rate was used; the bug had appeared in 0.3.37. - *) Bugfix: ngx_http_charset_module logged "unknown charset" alert, even + *) Bugfix: ngx_http_charset_module logged "unknown charset" alert, even if the recoding was not needed; the bug had appeared in 0.3.50. - *) Bugfix: if a code response of the PUT request was 409, then a + *) Bugfix: if a code response of the PUT request was 409, then a temporary file was not removed. Changes with nginx 0.3.51 30 Jun 2006 - *) Bugfix: the "<" symbols might disappeared some conditions in the - SSI; the bug had appeared in 0.3.50. + *) Bugfix: the "<" symbols might disappeared some conditions in the SSI; + the bug had appeared in 0.3.50. Changes with nginx 0.3.50 28 Jun 2006 - *) Change: the "proxy_redirect_errors" and "fastcgi_redirect_errors" - directives was renamed to the "proxy_intercept_errors" and + *) Change: the "proxy_redirect_errors" and "fastcgi_redirect_errors" + directives was renamed to the "proxy_intercept_errors" and "fastcgi_intercept_errors" directives. - *) Feature: the ngx_http_charset_module supports the recoding from the + *) Feature: the ngx_http_charset_module supports the recoding from the single byte encodings to the UTF-8 encoding and back. - *) Feature: the "X-Accel-Charset" response header line is supported in + *) Feature: the "X-Accel-Charset" response header line is supported in proxy and FastCGI mode. - *) Bugfix: the "\" escape symbol in the "\"" and "\'" pairs in the SSI + *) Bugfix: the "\" escape symbol in the "\"" and "\'" pairs in the SSI command was removed only if the command also has the "$" symbol. - *) Bugfix: the "<!--" string might be added on some conditions in the + *) Bugfix: the "<!--" string might be added on some conditions in the SSI after inclusion. - *) Bugfix: if the "Content-Length: 0" header line was in response, then + *) Bugfix: if the "Content-Length: 0" header line was in response, then in nonbuffered proxying mode the client connection was not closed. @@ -3660,26 +3664,26 @@ Changes with nginx 0.3.49 *) Bugfix: in the "set" directive. - *) Bugfix: if two or more FastCGI subrequests was in SSI, then first - subrequest output was included instead of second and following + *) Bugfix: if two or more FastCGI subrequests was in SSI, then first + subrequest output was included instead of second and following subrequests. Changes with nginx 0.3.48 29 May 2006 - *) Change: now the ngx_http_charset_module works for subrequests, if - the response has no "Content-Type" header line. - - *) Bugfix: if the "proxy_pass" directive has no URI part, then the - "proxy_redirect default" directive add the unnecessary slash in - start of the rewritten redirect. - - *) Bugfix: the internal redirect always transform client's HTTP method - to GET, now the transformation is made for the "X-Accel-Redirect" - redirects only and if the method is not HEAD; the bug had appeared - in 0.3.42. - - *) Bugfix: the ngx_http_perl_module could not be built, if the perl was + *) Change: now the ngx_http_charset_module works for subrequests, if the + response has no "Content-Type" header line. + + *) Bugfix: if the "proxy_pass" directive has no URI part, then the + "proxy_redirect default" directive add the unnecessary slash in start + of the rewritten redirect. + + *) Bugfix: the internal redirect always transform client's HTTP method + to GET, now the transformation is made for the "X-Accel-Redirect" + redirects only and if the method is not HEAD; the bug had appeared in + 0.3.42. + + *) Bugfix: the ngx_http_perl_module could not be built, if the perl was built with the threads support; the bug had appeared in 0.3.46. @@ -3687,42 +3691,42 @@ Changes with nginx 0.3.47 *) Feature: the "upstream" directive. - *) Change: now the "\" escape symbol in the "\"" and "\'" pairs in the + *) Change: now the "\" escape symbol in the "\"" and "\'" pairs in the SSI command is always removed. Changes with nginx 0.3.46 11 May 2006 - *) Feature: the "proxy_hide_header", "proxy_pass_header", + *) Feature: the "proxy_hide_header", "proxy_pass_header", "fastcgi_hide_header", and "fastcgi_pass_header" directives. - *) Change: the "proxy_pass_x_powered_by", "fastcgi_x_powered_by", and + *) Change: the "proxy_pass_x_powered_by", "fastcgi_x_powered_by", and "proxy_pass_server" directives were canceled. - *) Feature: the "X-Accel-Buffering" response header line is supported - in proxy mode. - - *) Bugfix: the reconfiguration bug and memory leaks in the + *) Feature: the "X-Accel-Buffering" response header line is supported in + proxy mode. + + *) Bugfix: the reconfiguration bug and memory leaks in the ngx_http_perl_module. Changes with nginx 0.3.45 06 May 2006 - *) Feature: the "ssl_verify_client", "ssl_verify_depth", and + *) Feature: the "ssl_verify_client", "ssl_verify_depth", and "ssl_client_certificate" directives. - *) Change: the $request_method variable now returns the main request + *) Change: the $request_method variable now returns the main request method. - *) Change: the ° symbol codes were changed in koi-win conversion + *) Change: the ° symbol codes were changed in koi-win conversion table. - *) Feature: the euro and N symbols were added to koi-win conversion + *) Feature: the euro and N symbols were added to koi-win conversion table. - *) Bugfix: if nginx distributed the requests among several backends and - some backend failed, then requests intended for this backend was - directed to one live backend only instead of being distributed among + *) Bugfix: if nginx distributed the requests among several backends and + some backend failed, then requests intended for this backend was + directed to one live backend only instead of being distributed among the rest. @@ -3730,7 +3734,7 @@ Changes with nginx 0.3.44 *) Feature: the "wait" parameter in the "include" SSI command. - *) Feature: the Ukrainian and Byelorussian characters were added to + *) Feature: the Ukrainian and Byelorussian characters were added to koi-win conversion table. *) Bugfix: in the SSI. @@ -3743,18 +3747,18 @@ Changes with nginx 0.3.43 Changes with nginx 0.3.42 26 Apr 2006 - *) Feature: the "bind" option of the "listen" directive in IMAP/POP3 + *) Feature: the "bind" option of the "listen" directive in IMAP/POP3 proxy. - *) Bugfix: if the same capture in the "rewrite" directive was used more + *) Bugfix: if the same capture in the "rewrite" directive was used more then once. - *) Bugfix: the $sent_http_content_type, $sent_http_content_length, - $sent_http_last_modified, $sent_http_connection, - $sent_http_keep_alive, and $sent_http_transfer_encoding variables + *) Bugfix: the $sent_http_content_type, $sent_http_content_length, + $sent_http_last_modified, $sent_http_connection, + $sent_http_keep_alive, and $sent_http_transfer_encoding variables were not written to access log. - *) Bugfix: the $sent_http_cache_control returned value of the single + *) Bugfix: the $sent_http_cache_control returned value of the single "Cache-Control" response header line. @@ -3762,13 +3766,13 @@ Changes with nginx 0.3.41 *) Feature: the -v switch. - *) Bugfix: the segmentation fault may occurred if the SSI page has + *) Bugfix: the segmentation fault may occurred if the SSI page has remote subrequests. *) Bugfix: in FastCGI handling. - *) Bugfix: if the perl modules path was not set using - --with-perl_modules_path=PATH or the "perl_modules", then the + *) Bugfix: if the perl modules path was not set using + --with-perl_modules_path=PATH or the "perl_modules", then the segmentation fault was occurred. @@ -3783,21 +3787,21 @@ Changes with nginx 0.3.40 Changes with nginx 0.3.39 17 Apr 2006 - *) Feature: the "uninitialized_variable_warn" directive; the logging - level of the "uninitialized variable" message was lowered from + *) Feature: the "uninitialized_variable_warn" directive; the logging + level of the "uninitialized variable" message was lowered from "alert" to "warn". *) Feature: the "override_charset" directive. - *) Change: now if the unknown variable is used in the "echo" and "if - expr='$name'" SSI-commands, then the "unknown variable" message is + *) Change: now if the unknown variable is used in the "echo" and "if + expr='$name'" SSI-commands, then the "unknown variable" message is not logged. - *) Bugfix: the active connection counter increased on the exceeding of - the connection limit specified by the "worker_connections" - directive; the bug had appeared in 0.2.0. - - *) Bugfix: the limit rate might not work on some condition; the bug had + *) Bugfix: the active connection counter increased on the exceeding of + the connection limit specified by the "worker_connections" directive; + the bug had appeared in 0.2.0. + + *) Bugfix: the limit rate might not work on some condition; the bug had appeared in 0.3.38. @@ -3808,20 +3812,20 @@ Changes with nginx 0.3.38 *) Change: the ngx_http_perl_module optimizations. Thanks to Sergey Skvortsov. - *) Feature: the ngx_http_perl_module supports the $r->request_body_file + *) Feature: the ngx_http_perl_module supports the $r->request_body_file method. *) Feature: the "client_body_in_file_only" directive. - *) Workaround: now on disk overflow nginx tries to write access logs + *) Workaround: now on disk overflow nginx tries to write access logs once a second only. Thanks to Anton Yuzhaninov and Maxim Dounin. - *) Bugfix: now the "limit_rate" directive more precisely limits rate if + *) Bugfix: now the "limit_rate" directive more precisely limits rate if rate is more than 100 Kbyte/s. Thanks to ForJest. - *) Bugfix: now the IMAP/POP3 proxy escapes the "\r" and "\n" symbols in + *) Bugfix: now the IMAP/POP3 proxy escapes the "\r" and "\n" symbols in login and password to pass authorization server. Thanks to Maxim Dounin. @@ -3830,10 +3834,10 @@ Changes with nginx 0.3.37 *) Feature: the "limit_except" directive. - *) Feature: the "if" directive supports the "!~", "!~*", "-f", and - "!-f" operators. - - *) Feature: the ngx_http_perl_module supports the $r->request_body + *) Feature: the "if" directive supports the "!~", "!~*", "-f", and "!-f" + operators. + + *) Feature: the ngx_http_perl_module supports the $r->request_body method. *) Bugfix: in the ngx_http_addition_filter_module. @@ -3843,37 +3847,37 @@ Changes with nginx 0.3.36 *) Feature: the ngx_http_addition_filter_module. - *) Feature: the "proxy_pass" and "fastcgi_pass" directives may be used + *) Feature: the "proxy_pass" and "fastcgi_pass" directives may be used inside the "if" block. - *) Feature: the "proxy_ignore_client_abort" and + *) Feature: the "proxy_ignore_client_abort" and "fastcgi_ignore_client_abort" directives. *) Feature: the "$request_completion" variable. - *) Feature: the ngx_http_perl_module supports the $r->request_method - and $r->remote_addr. + *) Feature: the ngx_http_perl_module supports the $r->request_method and + $r->remote_addr. *) Feature: the ngx_http_ssi_module supports the "elif" command. - *) Bugfix: the "\/" string in the expression of the "if" command of the + *) Bugfix: the "\/" string in the expression of the "if" command of the ngx_http_ssi_module was treated incorrectly. - *) Bugfix: in the regular expressions in the "if" command of the + *) Bugfix: in the regular expressions in the "if" command of the ngx_http_ssi_module. - *) Bugfix: if the relative path was specified in the - "client_body_temp_path", "proxy_temp_path", "fastcgi_temp_path", and - "perl_modules" directives, then the directory was used relatively to + *) Bugfix: if the relative path was specified in the + "client_body_temp_path", "proxy_temp_path", "fastcgi_temp_path", and + "perl_modules" directives, then the directory was used relatively to a current path but not to a server prefix. Changes with nginx 0.3.35 22 Mar 2006 - *) Bugfix: the accept-filter and the TCP_DEFER_ACCEPT option were set + *) Bugfix: the accept-filter and the TCP_DEFER_ACCEPT option were set for first "listen" directive only; the bug had appeared in 0.3.31. - *) Bugfix: in the "proxy_pass" directive without the URI part in a + *) Bugfix: in the "proxy_pass" directive without the URI part in a subrequest. @@ -3884,10 +3888,10 @@ Changes with nginx 0.3.34 Changes with nginx 0.3.33 15 Mar 2006 - *) Feature: the "http_503" parameter of the "proxy_next_upstream" or + *) Feature: the "http_503" parameter of the "proxy_next_upstream" or "fastcgi_next_upstream" directives. - *) Bugfix: ngx_http_perl_module did not work with inlined in the + *) Bugfix: ngx_http_perl_module did not work with inlined in the configuration code, if it was not started with the "sub" word. *) Bugfix: in the "post_action" directive. @@ -3895,7 +3899,7 @@ Changes with nginx 0.3.33 Changes with nginx 0.3.32 11 Mar 2006 - *) Bugfix: the debug logging on startup and reconfiguration time was + *) Bugfix: the debug logging on startup and reconfiguration time was removed; the bug had appeared in 0.3.31. @@ -3903,22 +3907,21 @@ Changes with nginx 0.3.31 *) Change: now nginx passes the malformed proxied backend responses. - *) Feature: the "listen" directives support the address in the "*:port" + *) Feature: the "listen" directives support the address in the "*:port" form. *) Feature: the EVFILER_TIMER support in MacOSX 10.4. - *) Workaround: for MacOSX 64-bit kernel kqueue millisecond timeout - bug. + *) Workaround: for MacOSX 64-bit kernel kqueue millisecond timeout bug. Thanks to Andrei Nigmatulin. - *) Bugfix: if there were several "listen" directives listening one - various addresses inside one server, then server names like - "*.domain.tld" worked for first address only; the bug had appeared - in 0.3.18. - - *) Bugfix: if the HTTPS protocol was used in the "proxy_pass" directive - and the request body was in temporary file then the request was not + *) Bugfix: if there were several "listen" directives listening one + various addresses inside one server, then server names like + "*.domain.tld" worked for first address only; the bug had appeared in + 0.3.18. + + *) Bugfix: if the HTTPS protocol was used in the "proxy_pass" directive + and the request body was in temporary file then the request was not transferred. *) Bugfix: perl 5.8.8 compatibility. @@ -3926,29 +3929,29 @@ Changes with nginx 0.3.31 Changes with nginx 0.3.30 22 Feb 2006 - *) Change: the ECONNABORTED error log level was changed to "error" from + *) Change: the ECONNABORTED error log level was changed to "error" from "crit". - *) Bugfix: the ngx_http_perl_module could not be build without the + *) Bugfix: the ngx_http_perl_module could not be build without the ngx_http_ssi_filter_module. - *) Bugfix: nginx could not be built on i386 platform, if the PIC was + *) Bugfix: nginx could not be built on i386 platform, if the PIC was used; the bug had appeared in 0.3.27. Changes with nginx 0.3.29 20 Feb 2006 - *) Feature: now nginx uses less memory, if PHP in FastCGI mode sends + *) Feature: now nginx uses less memory, if PHP in FastCGI mode sends many warnings before the response. - *) Bugfix: the "Transfer-Encoding: chunked" header line was issued in + *) Bugfix: the "Transfer-Encoding: chunked" header line was issued in the 204 responses for the HTTP/1.1 requests. - *) Bugfix: nginx returned the 502 response, if the complete response + *) Bugfix: nginx returned the 502 response, if the complete response header lines were transferred in a separate FastCGI records. - *) Bugfix: if the proxied URI was specified in the "post_action" - directive, then it ran only after a successful completion of a + *) Bugfix: if the proxied URI was specified in the "post_action" + directive, then it ran only after a successful completion of a request. @@ -3958,58 +3961,58 @@ Changes with nginx 0.3.28 *) Feature: the --with-cpu-opt=ppc64 configuration parameter. - *) Bugfix: on some condition the proxied connection with a client was + *) Bugfix: on some condition the proxied connection with a client was terminated prematurely. Thanks to Vladimir Shutoff. - *) Bugfix: the "X-Accel-Limit-Rate" header line was not taken into - account if the request was redirected using the "X-Accel-Redirect" + *) Bugfix: the "X-Accel-Limit-Rate" header line was not taken into + account if the request was redirected using the "X-Accel-Redirect" header line. - *) Bugfix: the "post_action" directive ran only after a successful + *) Bugfix: the "post_action" directive ran only after a successful completion of a request. - *) Bugfix: the proxied response body generated by the "post_action" + *) Bugfix: the proxied response body generated by the "post_action" directive was transferred to a client. Changes with nginx 0.3.27 08 Feb 2006 - *) Change: the "variables_hash_max_size" and + *) Change: the "variables_hash_max_size" and "variables_hash_bucket_size" directives. - *) Feature: the $body_bytes_sent variable can be used not only in the + *) Feature: the $body_bytes_sent variable can be used not only in the "log_format" directive. *) Feature: the $ssl_protocol and $ssl_cipher variables. - *) Feature: the cache line size detection for widespread CPUs at start + *) Feature: the cache line size detection for widespread CPUs at start time. - *) Feature: now the "accept_mutex" directive is supported using - fcntl(2) on platforms different from i386, amd64, sparc64, and ppc. - - *) Feature: the "lock_file" directive and the --with-lock-path=PATH + *) Feature: now the "accept_mutex" directive is supported using fcntl(2) + on platforms different from i386, amd64, sparc64, and ppc. + + *) Feature: the "lock_file" directive and the --with-lock-path=PATH autoconfiguration directive. - *) Bugfix: if the HTTPS protocol was used in the "proxy_pass" directive + *) Bugfix: if the HTTPS protocol was used in the "proxy_pass" directive then the requests with the body was not transferred. Changes with nginx 0.3.26 03 Feb 2006 - *) Change: the "optimize_host_names" directive was renamed to the + *) Change: the "optimize_host_names" directive was renamed to the "optimize_server_names". - *) Bugfix: if in the "proxy_pass" directive was no the URI part, then - the main request URI was transferred to a backend while proxying the + *) Bugfix: if in the "proxy_pass" directive was no the URI part, then + the main request URI was transferred to a backend while proxying the SSI subrequest. Changes with nginx 0.3.25 01 Feb 2006 - *) Bugfix: the segmentation fault was occurred on start or while - reconfiguration if there was invalid configuration; the bug had + *) Bugfix: the segmentation fault was occurred on start or while + reconfiguration if there was invalid configuration; the bug had appeared in 0.3.24. @@ -4017,16 +4020,16 @@ Changes with nginx 0.3.24 *) Workaround: for bug in FreeBSD kqueue. - *) Bugfix: now a response generated by the "post_action" directive is + *) Bugfix: now a response generated by the "post_action" directive is not transferred to a client. *) Bugfix: the memory leaks were occurring if many log files were used. - *) Bugfix: the first "proxy_redirect" directive was working inside one + *) Bugfix: the first "proxy_redirect" directive was working inside one location. - *) Bugfix: on 64-bit platforms segmentation fault may occurred on start - if the many names were used in the "server_name" directives; the bug + *) Bugfix: on 64-bit platforms segmentation fault may occurred on start + if the many names were used in the "server_name" directives; the bug had appeared in 0.3.18. @@ -4034,23 +4037,23 @@ Changes with nginx 0.3.23 *) Feature: the "optimize_host_names" directive. - *) Bugfix: in using of the variables in the "path" and "alias" + *) Bugfix: in using of the variables in the "path" and "alias" directives. - *) Bugfix: the ngx_http_perl_module was incorrectly built on Linux and + *) Bugfix: the ngx_http_perl_module was incorrectly built on Linux and Solaris. Changes with nginx 0.3.22 17 Jan 2006 - *) Feature: the ngx_http_perl_module supports the $r->args and + *) Feature: the ngx_http_perl_module supports the $r->args and $r->unescape methods. - *) Feature: the method $r->query_string of ngx_http_perl_module was + *) Feature: the method $r->query_string of ngx_http_perl_module was canceled. - *) Bugfix: segmentation fault was occurred if the "none" or "blocked" - values was specified in the "valid_referers" directive; the bug had + *) Bugfix: segmentation fault was occurred if the "none" or "blocked" + values was specified in the "valid_referers" directive; the bug had appeared in 0.3.18. @@ -4058,7 +4061,7 @@ Changes with nginx 0.3.21 *) Feature: the ngx_http_perl_module. - *) Change: the "valid_referers" directive allows the referreres without + *) Change: the "valid_referers" directive allows the referreres without URI part. @@ -4066,8 +4069,8 @@ Changes with nginx 0.3.20 *) Bugfix: in SSI handling. - *) Bugfix: the ngx_http_memcached_module did not support the keys in - the "/usr?args" form. + *) Bugfix: the ngx_http_memcached_module did not support the keys in the + "/usr?args" form. Changes with nginx 0.3.19 28 Dec 2005 @@ -4081,47 +4084,47 @@ Changes with nginx 0.3.19 Changes with nginx 0.3.18 26 Dec 2005 - *) Feature: the "server_names" directive supports the ".domain.tld" + *) Feature: the "server_names" directive supports the ".domain.tld" names. - *) Feature: the "server_names" directive uses the hash for the + *) Feature: the "server_names" directive uses the hash for the "*.domain.tld" names and more effective hash for usual names. - *) Change: the "server_names_hash_max_size" and + *) Change: the "server_names_hash_max_size" and "server_names_hash_bucket_size" directives. - *) Change: the "server_names_hash" and "server_names_hash_threshold" + *) Change: the "server_names_hash" and "server_names_hash_threshold" directives were canceled. *) Feature: the "valid_referers" directive uses the hash site names. - *) Change: now the "valid_referers" directive checks the site names - only without the URI part. - - *) Bugfix: some ".domain.tld" names incorrectly processed by the + *) Change: now the "valid_referers" directive checks the site names only + without the URI part. + + *) Bugfix: some ".domain.tld" names incorrectly processed by the ngx_http_map_module. - *) Bugfix: segmentation fault was occurred if configuration file did - not exist; the bug had appeared in 0.3.12. - - *) Bugfix: on 64-bit platforms segmentation fault may occurred on - start; the bug had appeared in 0.3.16. + *) Bugfix: segmentation fault was occurred if configuration file did not + exist; the bug had appeared in 0.3.12. + + *) Bugfix: on 64-bit platforms segmentation fault may occurred on start; + the bug had appeared in 0.3.16. Changes with nginx 0.3.17 18 Dec 2005 - *) Change: now on Linux configure checks the presence of epoll and + *) Change: now on Linux configure checks the presence of epoll and sendfile64() in kernel. - *) Feature: the "map" directive supports domain names in the + *) Feature: the "map" directive supports domain names in the ".domain.tld" form. - *) Bugfix: the timeouts were not used in SSL handshake; the bug had + *) Bugfix: the timeouts were not used in SSL handshake; the bug had appeared in 0.2.4. *) Bugfix: in the HTTPS protocol in the "proxy_pass" directive. - *) Bugfix: when the HTTPS protocol was used in the "proxy_pass" + *) Bugfix: when the HTTPS protocol was used in the "proxy_pass" directive the port 80 was used by default. @@ -4129,41 +4132,41 @@ Changes with nginx 0.3.16 *) Feature: the ngx_http_map_module. - *) Feature: the "types_hash_max_size" and "types_hash_bucket_size" + *) Feature: the "types_hash_max_size" and "types_hash_bucket_size" directives. *) Feature: the "ssi_value_length" directive. *) Feature: the "worker_rlimit_core" directive. - *) Workaround: the connection number in logs was always 1 if nginx was - built by the icc 8.1 or 9.0 compilers with optimization for + *) Workaround: the connection number in logs was always 1 if nginx was + built by the icc 8.1 or 9.0 compilers with optimization for Pentium 4. *) Bugfix: the "config timefmt" SSI command set incorrect time format. - *) Bugfix: nginx did not close connection to IMAP/POP3 backend for the + *) Bugfix: nginx did not close connection to IMAP/POP3 backend for the SSL connections; the bug had appeared in 0.3.13. Thanks to Rob Mueller. - *) Bugfix: segmentation fault may occurred in at SSL shutdown; the bug + *) Bugfix: segmentation fault may occurred in at SSL shutdown; the bug had appeared in 0.3.13. Changes with nginx 0.3.15 07 Dec 2005 - *) Feature: the new 444 code of the "return" directive to close + *) Feature: the new 444 code of the "return" directive to close connection. *) Feature: the "so_keepalive" directive in IMAP/POP3 proxy. - *) Bugfix: if there are unclosed connection nginx now calls abort() - only on gracefull quit and active "debug_points" directive. + *) Bugfix: if there are unclosed connection nginx now calls abort() only + on gracefull quit and active "debug_points" directive. Changes with nginx 0.3.14 05 Dec 2005 - *) Bugfix: in the 304 response the body was transferred; the bug had + *) Bugfix: in the 304 response the body was transferred; the bug had appeared in 0.3.13. @@ -4171,69 +4174,69 @@ Changes with nginx 0.3.13 *) Feature: the IMAP/POP3 proxy supports STARTTLS and STLS. - *) Bugfix: the IMAP/POP3 proxy did not work with the select, poll, and + *) Bugfix: the IMAP/POP3 proxy did not work with the select, poll, and /dev/poll methods. *) Bugfix: in SSI handling. - *) Bugfix: now Solaris sendfilev() is not used to transfer the client + *) Bugfix: now Solaris sendfilev() is not used to transfer the client request body to FastCGI-server via the unix domain socket. - *) Bugfix: the "auth_basic" directive did not disable the - authorization; the bug had appeared in 0.3.11. + *) Bugfix: the "auth_basic" directive did not disable the authorization; + the bug had appeared in 0.3.11. Changes with nginx 0.3.12 26 Nov 2005 - *) Security: if nginx was built with the ngx_http_realip_module and the - "satisfy_any on" directive was used, then access and authorization - directives did not work. The ngx_http_realip_module was not built - and is not built by default. + *) Security: if nginx was built with the ngx_http_realip_module and the + "satisfy_any on" directive was used, then access and authorization + directives did not work. The ngx_http_realip_module was not built and + is not built by default. *) Change: the "$time_gmt" variable name was changed to "$time_local". - *) Change: the "proxy_header_buffer_size" and - "fastcgi_header_buffer_size" directives was renamed to the + *) Change: the "proxy_header_buffer_size" and + "fastcgi_header_buffer_size" directives was renamed to the "proxy_buffer_size" and "fastcgi_buffer_size" directives. *) Feature: the ngx_http_memcached_module. *) Feature: the "proxy_buffering" directive. - *) Bugfix: the changes in accept mutex handling when the "rtsig" method + *) Bugfix: the changes in accept mutex handling when the "rtsig" method was used; the bug had appeared in 0.3.0. - *) Bugfix: if the client sent the "Transfer-Encoding: chunked" header + *) Bugfix: if the client sent the "Transfer-Encoding: chunked" header line, then nginx returns the 411 error. - *) Bugfix: if the "auth_basic" directive was inherited from the http - level, then the realm in the "WWW-Authenticate" header line was + *) Bugfix: if the "auth_basic" directive was inherited from the http + level, then the realm in the "WWW-Authenticate" header line was without the "Basic realm" text. - *) Bugfix: if the "combined" format was explicitly specified in the - "access_log" directive, then the empty lines was written to the log; + *) Bugfix: if the "combined" format was explicitly specified in the + "access_log" directive, then the empty lines was written to the log; the bug had appeared in 0.3.8. - *) Bugfix: nginx did not run on the sparc platform under any OS except + *) Bugfix: nginx did not run on the sparc platform under any OS except Solaris. - *) Bugfix: now it is not necessary to place space between the quoted + *) Bugfix: now it is not necessary to place space between the quoted string and closing bracket in the "if" directive. Changes with nginx 0.3.11 15 Nov 2005 - *) Bugfix: nginx did not pass the client request headers and body while + *) Bugfix: nginx did not pass the client request headers and body while proxying; the bug had appeared in 0.3.10. Changes with nginx 0.3.10 15 Nov 2005 - *) Change: the "valid_referers" directive and the "$invalid_referer" - variable were moved to the new ngx_http_referer_module from the + *) Change: the "valid_referers" directive and the "$invalid_referer" + variable were moved to the new ngx_http_referer_module from the ngx_http_rewrite_module. - *) Change: the "$apache_bytes_sent" variable name was changed to + *) Change: the "$apache_bytes_sent" variable name was changed to "$body_bytes_sent". *) Feature: the "$sent_http_..." variables. @@ -4250,73 +4253,73 @@ Changes with nginx 0.3.10 *) Feature: the "worker_cpu_affinity" directive for Linux. - *) Bugfix: the "rewrite" directive did not unescape URI part in - redirect, now it is unescaped except the %00-%25 and %7F-%FF + *) Bugfix: the "rewrite" directive did not unescape URI part in + redirect, now it is unescaped except the %00-%25 and %7F-%FF characters. *) Bugfix: nginx could not be built by the icc 9.0 compiler. - *) Bugfix: if the SSI was enabled for zero size static file, then the + *) Bugfix: if the SSI was enabled for zero size static file, then the chunked response was encoded incorrectly. Changes with nginx 0.3.9 10 Nov 2005 - *) Bugfix: nginx considered URI as unsafe if two any symbols was - between two slashes; the bug had appeared in 0.3.8. + *) Bugfix: nginx considered URI as unsafe if two any symbols was between + two slashes; the bug had appeared in 0.3.8. Changes with nginx 0.3.8 09 Nov 2005 - *) Security: nginx now checks URI got from a backend in - "X-Accel-Redirect" header line or in SSI file for the "/../" paths + *) Security: nginx now checks URI got from a backend in + "X-Accel-Redirect" header line or in SSI file for the "/../" paths and zeroes. - *) Change: nginx now does not treat the empty user name in the + *) Change: nginx now does not treat the empty user name in the "Authorization" header line as valid one. - *) Feature: the "ssl_session_timeout" directives of the + *) Feature: the "ssl_session_timeout" directives of the ngx_http_ssl_module and ngx_imap_ssl_module. - *) Feature: the "auth_http_header" directive of the + *) Feature: the "auth_http_header" directive of the ngx_imap_auth_http_module. *) Feature: the "add_header" directive. *) Feature: the ngx_http_realip_module. - *) Feature: the new variables to use in the "log_format" directive: - $bytes_sent, $apache_bytes_sent, $status, $time_gmt, $uri, - $request_time, $request_length, $upstream_status, - $upstream_response_time, $gzip_ratio, $uid_got, $uid_set, - $connection, $pipe, and $msec. The parameters in the "%name" form + *) Feature: the new variables to use in the "log_format" directive: + $bytes_sent, $apache_bytes_sent, $status, $time_gmt, $uri, + $request_time, $request_length, $upstream_status, + $upstream_response_time, $gzip_ratio, $uid_got, $uid_set, + $connection, $pipe, and $msec. The parameters in the "%name" form will be canceled soon. - *) Change: now the false variable values in the "if" directive are the + *) Change: now the false variable values in the "if" directive are the empty string "" and string starting with "0". - *) Bugfix: while using proxied or FastCGI-server nginx may leave + *) Bugfix: while using proxied or FastCGI-server nginx may leave connections and temporary files with client requests in open state. - *) Bugfix: the worker processes did not flush the buffered logs on + *) Bugfix: the worker processes did not flush the buffered logs on graceful exit. - *) Bugfix: if the request URI was changes by the "rewrite" directive - and the request was proxied in location given by regular expression, - then the incorrect request was transferred to backend; the bug had + *) Bugfix: if the request URI was changes by the "rewrite" directive and + the request was proxied in location given by regular expression, then + the incorrect request was transferred to backend; the bug had appeared in 0.2.6. - *) Bugfix: the "expires" directive did not remove the previous - "Expires" header. - - *) Bugfix: nginx may stop to accept requests if the "rtsig" method and + *) Bugfix: the "expires" directive did not remove the previous "Expires" + header. + + *) Bugfix: nginx may stop to accept requests if the "rtsig" method and several worker processes were used. - *) Bugfix: the "\"" and "\'" escape symbols were incorrectly handled in + *) Bugfix: the "\"" and "\'" escape symbols were incorrectly handled in SSI commands. - *) Bugfix: if the response was ended just after the SSI command and - gzipping was used, then the response did not transferred complete or + *) Bugfix: if the response was ended just after the SSI command and + gzipping was used, then the response did not transferred complete or did not transferred at all. @@ -4324,78 +4327,77 @@ Changes with nginx 0.3.7 *) Feature: the "access_log" supports the "buffer=" parameter. - *) Bugfix: nginx could not be built on platforms different from i386, + *) Bugfix: nginx could not be built on platforms different from i386, amd64, sparc, and ppc; the bug had appeared in 0.3.2. Changes with nginx 0.3.6 24 Oct 2005 - *) Change: now the IMAP/POP3 proxy do not send the empty login to + *) Change: now the IMAP/POP3 proxy do not send the empty login to authorization server. *) Feature: the "log_format" supports the variables in the $name form. - *) Bugfix: if at least in one server was no the "listen" directive, - then nginx did not listen on the 80 port; the bug had appeared in - 0.3.3. - - *) Bugfix: if the URI part is omitted in "proxy_pass" directive, the - the 80 port was always used. + *) Bugfix: if at least in one server was no the "listen" directive, then + nginx did not listen on the 80 port; the bug had appeared in 0.3.3. + + *) Bugfix: if the URI part is omitted in "proxy_pass" directive, the the + 80 port was always used. Changes with nginx 0.3.5 21 Oct 2005 - *) Bugfix: the segmentation fault may occurred if the IMAP/POP3 login + *) Bugfix: the segmentation fault may occurred if the IMAP/POP3 login was changed by authorization server; the bug had appeared in 0.2.2. - *) Bugfix: the accept mutex did not work and all connections were + *) Bugfix: the accept mutex did not work and all connections were handled by one process; the bug had appeared in 0.3.3. - *) Bugfix: the timeout did not work if the "rtsig" method and the + *) Bugfix: the timeout did not work if the "rtsig" method and the "timer_resolution" directive were used. Changes with nginx 0.3.4 19 Oct 2005 - *) Bugfix: nginx could not be built on Linux 2.4+ and MacOS X; the bug + *) Bugfix: nginx could not be built on Linux 2.4+ and MacOS X; the bug had appeared in 0.3.3. Changes with nginx 0.3.3 19 Oct 2005 - *) Change: the "bl" and "af" parameters of the "listen" directive was + *) Change: the "bl" and "af" parameters of the "listen" directive was renamed to the "backlog" and "accept_filter". - *) Feature: the "rcvbuf" and "sndbuf" parameters of the "listen" + *) Feature: the "rcvbuf" and "sndbuf" parameters of the "listen" directive. - *) Change: the "$msec" log parameter does not require now the - additional the gettimeofday() system call. + *) Change: the "$msec" log parameter does not require now the additional + the gettimeofday() system call. *) Feature: the -t switch now tests the "listen" directives. - *) Bugfix: if the invalid address was specified in the "listen" - directive, then after the -HUP signal nginx left an open socket in + *) Bugfix: if the invalid address was specified in the "listen" + directive, then after the -HUP signal nginx left an open socket in the CLOSED state. - *) Bugfix: the mime type may be incorrectly set to default value for + *) Bugfix: the mime type may be incorrectly set to default value for index file with variable in the name; the bug had appeared in 0.3.0. *) Feature: the "timer_resolution" directive. *) Feature: the millisecond "$upstream_response_time" log parameter. - *) Bugfix: a temporary file with client request body now is removed - just after the response header was transferred to a client. + *) Bugfix: a temporary file with client request body now is removed just + after the response header was transferred to a client. *) Bugfix: OpenSSL 0.9.6 compatibility. *) Bugfix: the SSL certificate and key file paths could not be relative. - *) Bugfix: the "ssl_prefer_server_ciphers" directive did not work in - the ngx_imap_ssl_module. - - *) Bugfix: the "ssl_protocols" directive allowed to specify the single + *) Bugfix: the "ssl_prefer_server_ciphers" directive did not work in the + ngx_imap_ssl_module. + + *) Bugfix: the "ssl_protocols" directive allowed to specify the single protocol only. @@ -4403,101 +4405,100 @@ Changes with nginx 0.3.2 *) Feature: the Sun Studio 10 C compiler support. - *) Feature: the "proxy_upstream_max_fails", - "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails", and + *) Feature: the "proxy_upstream_max_fails", + "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails", and "fastcgi_upstream_fail_timeout" directives. Changes with nginx 0.3.1 10 Oct 2005 - *) Bugfix: the segmentation fault occurred when the signal queue - overflowed if the "rtsig" method was used; the bug had appeared in + *) Bugfix: the segmentation fault occurred when the signal queue + overflowed if the "rtsig" method was used; the bug had appeared in 0.2.0. - *) Change: correct handling of the "\\", "\"", "\'", and "\$" pairs in + *) Change: correct handling of the "\\", "\"", "\'", and "\$" pairs in SSI. Changes with nginx 0.3.0 07 Oct 2005 - *) Change: the 10-days live time limit of worker process was - eliminated. The limit was introduced because of millisecond timers - overflow. + *) Change: the 10-days live time limit of worker process was eliminated. + The limit was introduced because of millisecond timers overflow. Changes with nginx 0.2.6 05 Oct 2005 - *) Change: while using load-balancing the time before the failed - backend retry was decreased from 60 to 10 seconds. - - *) Change: the "proxy_pass_unparsed_uri" was canceled, the original URI + *) Change: while using load-balancing the time before the failed backend + retry was decreased from 60 to 10 seconds. + + *) Change: the "proxy_pass_unparsed_uri" was canceled, the original URI now passed, if the URI part is omitted in "proxy_pass" directive. - *) Feature: the "error_page" directive supports redirects and allows + *) Feature: the "error_page" directive supports redirects and allows more flexible to change an error code. - *) Change: the charset in the "Content-Type" header line now is ignored + *) Change: the charset in the "Content-Type" header line now is ignored in proxied subrequests. - *) Bugfix: if the URI was changed in the "if" block and request did not - found new configuration, then the ngx_http_rewrite_module rules ran + *) Bugfix: if the URI was changed in the "if" block and request did not + found new configuration, then the ngx_http_rewrite_module rules ran again. - *) Bugfix: if the "set" directive set the ngx_http_geo_module variable - in some configuration part, the this variable was not available in - other configuration parts and the "using uninitialized variable" + *) Bugfix: if the "set" directive set the ngx_http_geo_module variable + in some configuration part, the this variable was not available in + other configuration parts and the "using uninitialized variable" error was occurred; the bug had appeared in 0.2.2. Changes with nginx 0.2.5 04 Oct 2005 - *) Change: the duplicate value of the ngx_http_geo_module variable now + *) Change: the duplicate value of the ngx_http_geo_module variable now causes the warning and changes old value. *) Feature: the ngx_http_ssi_module supports the "set" command. - *) Feature: the ngx_http_ssi_module supports the "file" parameter in - the "include" command. - - *) Feature: the ngx_http_ssi_module supports the variable value + *) Feature: the ngx_http_ssi_module supports the "file" parameter in the + "include" command. + + *) Feature: the ngx_http_ssi_module supports the variable value substitutions in expressions of the "if" command. Changes with nginx 0.2.4 03 Oct 2005 - *) Feature: the ngx_http_ssi_module supports "$var=text", "$var!=text", + *) Feature: the ngx_http_ssi_module supports "$var=text", "$var!=text", "$var=/text/", and "$var!=/text/" expressions in the "if" command. - *) Bugfix: in proxying location without trailing slash; the bug had + *) Bugfix: in proxying location without trailing slash; the bug had appeared in 0.1.44. - *) Bugfix: the segmentation fault may occurred if the "rtsig" method - was used; the bug had appeared in 0.2.0. + *) Bugfix: the segmentation fault may occurred if the "rtsig" method was + used; the bug had appeared in 0.2.0. Changes with nginx 0.2.3 30 Sep 2005 - *) Bugfix: nginx could not be built without the --with-debug option; - the bug had appeared in 0.2.2. + *) Bugfix: nginx could not be built without the --with-debug option; the + bug had appeared in 0.2.2. Changes with nginx 0.2.2 30 Sep 2005 *) Feature: the "config errmsg" command of the ngx_http_ssi_module. - *) Change: the ngx_http_geo_module variables can be overridden by the + *) Change: the ngx_http_geo_module variables can be overridden by the "set" directive. - *) Feature: the "ssl_protocols" and "ssl_prefer_server_ciphers" + *) Feature: the "ssl_protocols" and "ssl_prefer_server_ciphers" directives of the ngx_http_ssl_module and ngx_imap_ssl_module. - *) Bugfix: the ngx_http_autoindex_module did not show correctly the - long file names; - - *) Bugfix: the ngx_http_autoindex_module now do not show the files + *) Bugfix: the ngx_http_autoindex_module did not show correctly the long + file names; + + *) Bugfix: the ngx_http_autoindex_module now do not show the files starting by dot. - *) Bugfix: if the SSL handshake failed then another connection may be + *) Bugfix: if the SSL handshake failed then another connection may be closed too. Thanks to Rob Mueller. @@ -4506,36 +4507,36 @@ Changes with nginx 0.2.2 Changes with nginx 0.2.1 23 Sep 2005 - *) Bugfix: if all backend using in load-balancing failed after one - error, then nginx may got caught in an endless loop; the bug had + *) Bugfix: if all backend using in load-balancing failed after one + error, then nginx may got caught in an endless loop; the bug had appeared in 0.2.0. Changes with nginx 0.2.0 23 Sep 2005 - *) The pid-file names used during online upgrade was changed and now is - not required a manual rename operation. The old master process adds - the ".oldbin" suffix to its pid-file and executes a new binary file. - The new master process creates usual pid-file without the ".newbin" - suffix. If the master process exits, then old master process renames - back its pid-file with the ".oldbin" suffix to the pid-file without + *) The pid-file names used during online upgrade was changed and now is + not required a manual rename operation. The old master process adds + the ".oldbin" suffix to its pid-file and executes a new binary file. + The new master process creates usual pid-file without the ".newbin" + suffix. If the master process exits, then old master process renames + back its pid-file with the ".oldbin" suffix to the pid-file without suffix. - *) Change: the "worker_connections" directive, new name of the - "connections" directive; now the directive specifies maximum number + *) Change: the "worker_connections" directive, new name of the + "connections" directive; now the directive specifies maximum number of connections, but not maximum socket descriptor number. *) Feature: SSL supports the session cache inside one worker process. *) Feature: the "satisfy_any" directive. - *) Change: the ngx_http_access_module and ngx_http_auth_basic_module do + *) Change: the ngx_http_access_module and ngx_http_auth_basic_module do not run for subrequests. - *) Feature: the "worker_rlimit_nofile" and "worker_rlimit_sigpending" + *) Feature: the "worker_rlimit_nofile" and "worker_rlimit_sigpending" directives. - *) Bugfix: if all backend using in load-balancing failed after one + *) Bugfix: if all backend using in load-balancing failed after one error, then nginx did not try do connect to them during 60 seconds. *) Bugfix: in IMAP/POP3 command argument parsing. @@ -4545,17 +4546,17 @@ Changes with nginx 0.2.0 *) Bugfix: errors while using SSI and gzipping. - *) Bugfix: the "Expires" and "Cache-Control" header lines were omitted + *) Bugfix: the "Expires" and "Cache-Control" header lines were omitted from the 304 responses. Thanks to Alexandr Kukushkin. Changes with nginx 0.1.45 08 Sep 2005 - *) Change: the "ssl_engine" directive was canceled in the + *) Change: the "ssl_engine" directive was canceled in the ngx_http_ssl_module and now is introduced at global level. - *) Bugfix: the responses with SSI subrequests did not transferred via + *) Bugfix: the responses with SSI subrequests did not transferred via SSL connection. *) Various bug fixes in the IMAP/POP3 proxy. @@ -4569,126 +4570,126 @@ Changes with nginx 0.1.44 *) Feature: the "userid_mark" directive. - *) Feature: the $remote_user variable value is determined independently + *) Feature: the $remote_user variable value is determined independently of authorization use. Changes with nginx 0.1.43 30 Aug 2005 - *) Feature: the listen(2) backlog in the "listen" directive can be + *) Feature: the listen(2) backlog in the "listen" directive can be changed using the -HUP signal. *) Feature: the geo2nginx.pl script was added to contrib. - *) Change: the FastCGI parameters with the empty values now are passed + *) Change: the FastCGI parameters with the empty values now are passed to a server. - *) Bugfix: the segmentation fault occurred or the worker process may - got caught in an endless loop if the proxied or FastCGI server sent - the "Cache-Control" header line and the "expires" directive was - used; in the proxied mode the the bug had appeared in 0.1.29. + *) Bugfix: the segmentation fault occurred or the worker process may got + caught in an endless loop if the proxied or FastCGI server sent the + "Cache-Control" header line and the "expires" directive was used; in + the proxied mode the the bug had appeared in 0.1.29. Changes with nginx 0.1.42 23 Aug 2005 - *) Bugfix: if the request URI had a zero length after the processing in - the ngx_http_proxy_module, then the segmentation fault or bus error + *) Bugfix: if the request URI had a zero length after the processing in + the ngx_http_proxy_module, then the segmentation fault or bus error occurred in the ngx_http_proxy_module. - *) Bugfix: the "limit_rate" directive did not work inside the "if" + *) Bugfix: the "limit_rate" directive did not work inside the "if" block; the bug had appeared in 0.1.38. Changes with nginx 0.1.41 25 Jul 2005 - *) Bugfix: if the variable was used in the configuration file, then it + *) Bugfix: if the variable was used in the configuration file, then it can not be used in SSI. Changes with nginx 0.1.40 22 Jul 2005 - *) Bugfix: if a client sent too long header line, then the request + *) Bugfix: if a client sent too long header line, then the request information did not logged in the error log. - *) Bugfix: the "Set-Cookie" header line was not transferred when the + *) Bugfix: the "Set-Cookie" header line was not transferred when the "X-Accel-Redirect" was used; the bug had appeared in 0.1.39. - *) Bugfix: the "Content-Disposition" header line was not transferred + *) Bugfix: the "Content-Disposition" header line was not transferred when the "X-Accel-Redirect" was used. - *) Bugfix: the master process did not close the listen socket on the + *) Bugfix: the master process did not close the listen socket on the SIGQUIT signal. - *) Bugfix: after on-line upgrade on Linux and Solaris the process name + *) Bugfix: after on-line upgrade on Linux and Solaris the process name became shorter in the "ps" command. Changes with nginx 0.1.39 14 Jul 2005 - *) The changes in the ngx_http_charset_module: the "default_charset" - directive was canceled; the "charset" directive sets the response + *) The changes in the ngx_http_charset_module: the "default_charset" + directive was canceled; the "charset" directive sets the response charset; the "source_charset" directive sets the source charset only. - *) Bugfix: the backend "WWW-Authenticate" header line did not + *) Bugfix: the backend "WWW-Authenticate" header line did not transferred while the 401 response code redirecting. - *) Bugfix: the ngx_http_proxy_module and ngx_http_fastcgi_module may - close a connection before anything was transferred to a client; the + *) Bugfix: the ngx_http_proxy_module and ngx_http_fastcgi_module may + close a connection before anything was transferred to a client; the bug had appeared in 0.1.38. *) Workaround: the Linux glibc crypt_r() initialization bug. - *) Bugfix: the ngx_http_ssi_module did not support the relative URI in + *) Bugfix: the ngx_http_ssi_module did not support the relative URI in the "include virtual" command. - *) Bugfix: if the backend response had the "Location" header line and - nginx should not rewrite this line, then the 500 code response body + *) Bugfix: if the backend response had the "Location" header line and + nginx should not rewrite this line, then the 500 code response body was transferred; the bug had appeared in 0.1.29. - *) Bugfix: some directives of the ngx_http_proxy_module and - ngx_http_fastcgi_module were not inherited from the server to the + *) Bugfix: some directives of the ngx_http_proxy_module and + ngx_http_fastcgi_module were not inherited from the server to the location level; the bug had appeared in 0.1.29. - *) Bugfix: the ngx_http_ssl_module did not support the certificate + *) Bugfix: the ngx_http_ssl_module did not support the certificate chain. - *) Bugfix: the ngx_http_autoindex_module did not show correctly the - long file names; the bug had appeared in 0.1.38. - - *) Bugfixes in IMAP/POP3 proxy in interaction with a backend at the + *) Bugfix: the ngx_http_autoindex_module did not show correctly the long + file names; the bug had appeared in 0.1.38. + + *) Bugfixes in IMAP/POP3 proxy in interaction with a backend at the login state. Changes with nginx 0.1.38 08 Jul 2005 - *) Feature: the "limit_rate" directive is supported in in proxy and + *) Feature: the "limit_rate" directive is supported in in proxy and FastCGI mode. - *) Feature: the "X-Accel-Limit-Rate" response header line is supported + *) Feature: the "X-Accel-Limit-Rate" response header line is supported in proxy and FastCGI mode. *) Feature: the "break" directive. *) Feature: the "log_not_found" directive. - *) Bugfix: the response status code was not changed when request was + *) Bugfix: the response status code was not changed when request was redirected by the ""X-Accel-Redirect" header line. - *) Bugfix: the variables set by the "set" directive could not be used - in SSI. - - *) Bugfix: the segmentation fault may occurred if the SSI page has more + *) Bugfix: the variables set by the "set" directive could not be used in + SSI. + + *) Bugfix: the segmentation fault may occurred if the SSI page has more than one remote subrequest. - *) Bugfix: nginx treated the backend response as invalid if the status - line in the header was transferred in two packets; the bug had + *) Bugfix: nginx treated the backend response as invalid if the status + line in the header was transferred in two packets; the bug had appeared in 0.1.29. *) Feature: the "ssi_types" directive. *) Feature: the "autoindex_exact_size" directive. - *) Bugfix: the ngx_http_autoindex_module did not support the long file + *) Bugfix: the ngx_http_autoindex_module did not support the long file names in UTF-8. *) Feature: the IMAP/POP3 proxy. @@ -4698,34 +4699,34 @@ Changes with nginx 0.1.37 *) Change: now the "\n" is added to the end of the "nginx.pid" file. - *) Bugfix: the responses may be transferred not completely, if many + *) Bugfix: the responses may be transferred not completely, if many parts or the big parts were included by SSI. - *) Bugfix: if all backends had returned the 404 reponse and the - "http_404" parameter of the "proxy_next_upstream" or - "fastcgi_next_upstream" directives was used, then nginx started to + *) Bugfix: if all backends had returned the 404 reponse and the + "http_404" parameter of the "proxy_next_upstream" or + "fastcgi_next_upstream" directives was used, then nginx started to request all backends again. Changes with nginx 0.1.36 15 Jun 2005 - *) Change: if the request header has duplicate the "Host", - "Connection", "Content-Length", or "Authorization" lines, then nginx - now returns the 400 error. + *) Change: if the request header has duplicate the "Host", "Connection", + "Content-Length", or "Authorization" lines, then nginx now returns + the 400 error. *) Change: the "post_accept_timeout" directive was canceled. - *) Feature: the "default", "af=", "bl=", "deferred", and "bind" + *) Feature: the "default", "af=", "bl=", "deferred", and "bind" parameters of the "listen" directive. *) Feature: the FreeBSD accept filters support. *) Feature: the Linux TCP_DEFER_ACCEPT support. - *) Bugfix: the ngx_http_autoindex_module did not support the file names + *) Bugfix: the ngx_http_autoindex_module did not support the file names in UTF-8. - *) Bugfix: the new log file can be rotated by the -USR1 signal only if + *) Bugfix: the new log file can be rotated by the -USR1 signal only if the reconfiguration by the -HUP signal was made twice. @@ -4735,61 +4736,61 @@ Changes with nginx 0.1.35 *) Feature: the "port_in_redirect" directive. - *) Bugfix: the segmentation fault was occurred if the backend response + *) Bugfix: the segmentation fault was occurred if the backend response header was in several packets; the bug had appeared in 0.1.29. - *) Bugfix: if more than 10 servers were configured or some server did - not use the "listen" directive, then the segmentation fault was + *) Bugfix: if more than 10 servers were configured or some server did + not use the "listen" directive, then the segmentation fault was occurred on the start. - *) Bugfix: the segmentation fault might occur if the response was - bigger than the temporary file. - - *) Bugfix: nginx returned the 400 response on requests like - "GET http://www.domain.com/uri HTTP/1.0"; the bug had appeared in + *) Bugfix: the segmentation fault might occur if the response was bigger + than the temporary file. + + *) Bugfix: nginx returned the 400 response on requests like + "GET http://www.domain.com/uri HTTP/1.0"; the bug had appeared in 0.1.28. Changes with nginx 0.1.34 26 May 2005 - *) Bugfix: the worker process may got caught in an endless loop if the + *) Bugfix: the worker process may got caught in an endless loop if the big response part were include by SSI. - *) Bugfix: the variables set by the "set" directive were not available + *) Bugfix: the variables set by the "set" directive were not available in SSI. *) Feature: the "autoindex_localtime" directive. - *) Bugfix: the empty value of the "proxy_set_header" directive forbids + *) Bugfix: the empty value of the "proxy_set_header" directive forbids the client request header line passing. Changes with nginx 0.1.33 23 May 2005 - *) Bugfix: nginx could not be built with the --without-pcre parameter; + *) Bugfix: nginx could not be built with the --without-pcre parameter; the bug had appeared in 0.1.29. - *) Bugfix: 3, 4, 7, and 8 the "proxy_set_header" directives in one - level cause the bus fault on start up. + *) Bugfix: 3, 4, 7, and 8 the "proxy_set_header" directives in one level + cause the bus fault on start up. *) Bugfix: the HTTP protocol was specified in the HTTPS redirects. - *) Bugfix: if the "rewrite" directive used the captures inside the "if" + *) Bugfix: if the "rewrite" directive used the captures inside the "if" directive, then the 500 error code was returned. Changes with nginx 0.1.32 19 May 2005 - *) Bugfix: the arguments were omitted in the redirects, issued by the + *) Bugfix: the arguments were omitted in the redirects, issued by the "rewrite" directive; the bug had appeared in 0.1.29. - *) Feature: the "if" directive supports the captures in regular + *) Feature: the "if" directive supports the captures in regular expressions. - *) Feature: the "set" directive supports the variables and the captures + *) Feature: the "set" directive supports the variables and the captures of regular expressions. - *) Feature: the "X-Accel-Redirect" response header line is supported in + *) Feature: the "X-Accel-Redirect" response header line is supported in proxy and FastCGI mode. @@ -4801,23 +4802,23 @@ Changes with nginx 0.1.31 *) Bugfix: errors while using SSI and gzipping. - *) Bugfix: the redirect with the 301 code was transferred without + *) Bugfix: the redirect with the 301 code was transferred without response body; the bug had appeared in 0.1.30. Changes with nginx 0.1.30 14 May 2005 - *) Bugfix: the worker process may got caught in an endless loop if the + *) Bugfix: the worker process may got caught in an endless loop if the SSI was used. *) Bugfix: the response encrypted by SSL may not transferred complete. - *) Bugfix: if the length of the response part received at once from - proxied or FastCGI server was equal to 500, then nginx returns the - 500 response code; in proxy mode the the bug had appeared in 0.1.29 + *) Bugfix: if the length of the response part received at once from + proxied or FastCGI server was equal to 500, then nginx returns the + 500 response code; in proxy mode the the bug had appeared in 0.1.29 only. - *) Bugfix: nginx did not consider the directives with 8 or 9 parameters + *) Bugfix: nginx did not consider the directives with 8 or 9 parameters as invalid. *) Feature: the "return" directive can return the 204 response code. @@ -4829,47 +4830,47 @@ Changes with nginx 0.1.29 *) Feature: the ngx_http_ssi_module supports "include virtual" command. - *) Feature: the ngx_http_ssi_module supports the condition command like - 'if expr="$NAME"' and "else" and "endif" commands. Only one nested + *) Feature: the ngx_http_ssi_module supports the condition command like + 'if expr="$NAME"' and "else" and "endif" commands. Only one nested level is supported. - *) Feature: the ngx_http_ssi_module supports the DATE_LOCAL and - DATE_GMT variables and "config timefmt" command. + *) Feature: the ngx_http_ssi_module supports the DATE_LOCAL and DATE_GMT + variables and "config timefmt" command. *) Feature: the "ssi_ignore_recycled_buffers" directive. - *) Bugfix: the "echo" command did not show the default value for the + *) Bugfix: the "echo" command did not show the default value for the empty QUERY_STRING variable. *) Change: the ngx_http_proxy_module was rewritten. - *) Feature: the "proxy_redirect", "proxy_pass_request_headers", + *) Feature: the "proxy_redirect", "proxy_pass_request_headers", "proxy_pass_request_body", and "proxy_method" directives. - *) Feature: the "proxy_set_header" directive. The "proxy_x_var" was + *) Feature: the "proxy_set_header" directive. The "proxy_x_var" was canceled and must be replaced with the proxy_set_header directive. - *) Change: the "proxy_preserve_host" is canceled and must be replaced - with the "proxy_set_header Host $host" and the "proxy_redirect off" - directives, the "proxy_set_header Host $host:$proxy_port" directive + *) Change: the "proxy_preserve_host" is canceled and must be replaced + with the "proxy_set_header Host $host" and the "proxy_redirect off" + directives, the "proxy_set_header Host $host:$proxy_port" directive and the appropriate proxy_redirect directives. - *) Change: the "proxy_set_x_real_ip" is canceled and must be replaced + *) Change: the "proxy_set_x_real_ip" is canceled and must be replaced with the "proxy_set_header X-Real-IP $remote_addr" directive. - *) Change: the "proxy_add_x_forwarded_for" is canceled and must be - replaced with - the "proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for" + *) Change: the "proxy_add_x_forwarded_for" is canceled and must be + replaced with + the "proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for" directive. - *) Change: the "proxy_set_x_url" is canceled and must be replaced with - the "proxy_set_header X-URL http://$host:$server_port$request_uri" + *) Change: the "proxy_set_x_url" is canceled and must be replaced with + the "proxy_set_header X-URL http://$host:$server_port$request_uri" directive. *) Feature: the "fastcgi_param" directive. - *) Change: the "fastcgi_root", "fastcgi_set_var" and "fastcgi_params" - directive are canceled and must be replaced with the fastcgi_param + *) Change: the "fastcgi_root", "fastcgi_set_var" and "fastcgi_params" + directive are canceled and must be replaced with the fastcgi_param directives. *) Feature: the "index" directive can use the variables. @@ -4882,32 +4883,32 @@ Changes with nginx 0.1.29 *) Feature: the "internal" directive. - *) Feature: the CONTENT_LENGTH, CONTENT_TYPE, REMOTE_PORT, SERVER_ADDR, - SERVER_PORT, SERVER_PROTOCOL, DOCUMENT_ROOT, SERVER_NAME, + *) Feature: the CONTENT_LENGTH, CONTENT_TYPE, REMOTE_PORT, SERVER_ADDR, + SERVER_PORT, SERVER_PROTOCOL, DOCUMENT_ROOT, SERVER_NAME, REQUEST_METHOD, REQUEST_URI, and REMOTE_USER variables. - *) Change: nginx now passes the invalid lines in a client request + *) Change: nginx now passes the invalid lines in a client request headers or a backend response header. - *) Bugfix: if the backend did not transfer response for a long time and - the "send_timeout" was less than "proxy_read_timeout", then nginx + *) Bugfix: if the backend did not transfer response for a long time and + the "send_timeout" was less than "proxy_read_timeout", then nginx returned the 408 response. - *) Bugfix: the segmentation fault was occurred if the backend sent an + *) Bugfix: the segmentation fault was occurred if the backend sent an invalid line in response header; the bug had appeared in 0.1.26. - *) Bugfix: the segmentation fault may occurred in FastCGI fault + *) Bugfix: the segmentation fault may occurred in FastCGI fault tolerance configuration. - *) Bugfix: the "expires" directive did not remove the previous - "Expires" and "Cache-Control" headers. - - *) Bugfix: nginx did not take into account trailing dot in "Host" - header line. + *) Bugfix: the "expires" directive did not remove the previous "Expires" + and "Cache-Control" headers. + + *) Bugfix: nginx did not take into account trailing dot in "Host" header + line. *) Bugfix: the ngx_http_auth_module did not work under Linux. - *) Bugfix: the rewrite directive worked incorrectly, if the arguments + *) Bugfix: the rewrite directive worked incorrectly, if the arguments were in a request. *) Bugfix: nginx could not be built on MacOS X. @@ -4924,55 +4925,55 @@ Changes with nginx 0.1.27 *) Feature: the "blocked" parameter of the "valid_referers" directive. - *) Change: the errors while handling the request header now logged at - "info" level. The server name and the "Host" and "Referer" header + *) Change: the errors while handling the request header now logged at + "info" level. The server name and the "Host" and "Referer" header lines also logged. *) Change: the "Host" header line is also logged in error log. - *) Feature: the proxy_pass_unparsed_uri directive. The special handling - of the "://" symbols in URI, appeared in 0.1.11 version, now is + *) Feature: the proxy_pass_unparsed_uri directive. The special handling + of the "://" symbols in URI, appeared in 0.1.11 version, now is canceled. - *) Bugfix: nginx could not be built on FreeBSD and Linux, if the - --without-ngx_http_auth_basic_module configuration parameter was + *) Bugfix: nginx could not be built on FreeBSD and Linux, if the + --without-ngx_http_auth_basic_module configuration parameter was used. Changes with nginx 0.1.26 22 Mar 2005 - *) Change: the invalid client header lines are now ignored and logged - at the info level. + *) Change: the invalid client header lines are now ignored and logged at + the info level. *) Change: the server name is also logged in error log. - *) Feature: the ngx_http_auth_basic_module module and the auth_basic - and auth_basic_user_file directives. + *) Feature: the ngx_http_auth_basic_module module and the auth_basic and + auth_basic_user_file directives. Changes with nginx 0.1.25 19 Mar 2005 *) Bugfix: nginx did run on Linux parisc. - *) Feature: nginx now does not start under FreeBSD if the sysctl + *) Feature: nginx now does not start under FreeBSD if the sysctl kern.ipc.somaxconn value is too big. - *) Bugfix: if a request was internally redirected by the - ngx_http_index_module module to the ngx_http_proxy_module or - ngx_http_fastcgi_module modules, then the index file was not closed + *) Bugfix: if a request was internally redirected by the + ngx_http_index_module module to the ngx_http_proxy_module or + ngx_http_fastcgi_module modules, then the index file was not closed after request completion. - *) Feature: the "proxy_pass" can be used in location with regular + *) Feature: the "proxy_pass" can be used in location with regular expression. - *) Feature: the ngx_http_rewrite_filter_module module supports the + *) Feature: the ngx_http_rewrite_filter_module module supports the condition like "if ($HTTP_USER_AGENT ~ MSIE)". - *) Bugfix: nginx started too slow if the large number of addresses and + *) Bugfix: nginx started too slow if the large number of addresses and text values were used in the "geo" directive. - *) Change: a variable name must be declared as "$name" in the "geo" - directive. The previous variant without "$" is still supported, but + *) Change: a variable name must be declared as "$name" in the "geo" + directive. The previous variant without "$" is still supported, but will be removed soon. *) Feature: the "%{VARIABLE}v" logging parameter. @@ -4986,58 +4987,58 @@ Changes with nginx 0.1.25 Changes with nginx 0.1.24 04 Mar 2005 - *) Feature: the ngx_http_ssi_filter_module supports the QUERY_STRING - and DOCUMENT_URI variables. - - *) Bugfix: the ngx_http_autoindex_module may some times return the 404 - response for existent directory, if this directory was used in + *) Feature: the ngx_http_ssi_filter_module supports the QUERY_STRING and + DOCUMENT_URI variables. + + *) Bugfix: the ngx_http_autoindex_module may some times return the 404 + response for existent directory, if this directory was used in "alias" directive. - *) Bugfix: the ngx_http_ssi_filter_module ran incorrectly for large + *) Bugfix: the ngx_http_ssi_filter_module ran incorrectly for large responses. - *) Bugfix: the lack of the "Referer" header line was always accounted - as valid referrer. + *) Bugfix: the lack of the "Referer" header line was always accounted as + valid referrer. Changes with nginx 0.1.23 01 Mar 2005 - *) Feature: the ngx_http_ssi_filter_module and the ssi, - ssi_silent_errors, and ssi_min_file_chunk directives. The 'echo - var="HTTP_..." default=""' and 'echo var="REMOTE_ADDR"' commands are + *) Feature: the ngx_http_ssi_filter_module and the ssi, + ssi_silent_errors, and ssi_min_file_chunk directives. The 'echo + var="HTTP_..." default=""' and 'echo var="REMOTE_ADDR"' commands are supported. *) Feature: the %request_time log parameter. - *) Feature: if the request has no the "Host" header line, then the - "proxy_preserve_host" directive set this header line to the first + *) Feature: if the request has no the "Host" header line, then the + "proxy_preserve_host" directive set this header line to the first server name of the "server_name" directive. - *) Bugfix: nginx could not be built on platforms different from i386, + *) Bugfix: nginx could not be built on platforms different from i386, amd64, sparc, and ppc; the bug had appeared in 0.1.22. - *) Bugfix: the ngx_http_autoindex_module now shows the information not + *) Bugfix: the ngx_http_autoindex_module now shows the information not about the symlink, but about file or directory it points to. - *) Bugfix: the %apache_length parameter logged the negative length of + *) Bugfix: the %apache_length parameter logged the negative length of the response header if the no response was transferred to a client. Changes with nginx 0.1.22 22 Feb 2005 - *) Bugfix: the ngx_http_stub_status_module showed incorrect handled + *) Bugfix: the ngx_http_stub_status_module showed incorrect handled connections statistics if the proxying or FastCGI server were used. - *) Bugfix: the installation paths were incorrectly quoted on Linux and + *) Bugfix: the installation paths were incorrectly quoted on Linux and Solaris; the bug had appeared in 0.1.21. Changes with nginx 0.1.21 22 Feb 2005 - *) Bugfix: the ngx_http_stub_status_module showed incorrect statistics + *) Bugfix: the ngx_http_stub_status_module showed incorrect statistics if "rtsig" method was used or if several worker process ran on SMP. - *) Bugfix: nginx could not be built by the icc compiler on Linux or if + *) Bugfix: nginx could not be built by the icc compiler on Linux or if the zlib-1.2.x library was building from sources. *) Bugfix: nginx could not be built on NetBSD 2.0. @@ -5045,7 +5046,7 @@ Changes with nginx 0.1.21 Changes with nginx 0.1.20 17 Feb 2005 - *) Feature: the new "script_filename" and "remote_port" parameters of + *) Feature: the new "script_filename" and "remote_port" parameters of the fastcgi_params directive. *) Bugfix: the FastCGI stderr stream was handled incorrectly. @@ -5053,68 +5054,68 @@ Changes with nginx 0.1.20 Changes with nginx 0.1.19 16 Feb 2005 - *) Bugfix: now, if request contains the zero, then the 404 error is + *) Bugfix: now, if request contains the zero, then the 404 error is returned for the local requests. *) Bugfix: nginx could not be built on NetBSD 2.0. - *) Bugfix: the timeout may occur while reading of the the client - request body via SSL connections. + *) Bugfix: the timeout may occur while reading of the the client request + body via SSL connections. Changes with nginx 0.1.18 09 Feb 2005 - *) Workaround: the default values of the devpoll_events and the - devpoll_changes directives changed from 512 to 32 to be compatible + *) Workaround: the default values of the devpoll_events and the + devpoll_changes directives changed from 512 to 32 to be compatible with Solaris 10. - *) Bugfix: the proxy_set_x_var and fastcgi_set_var directives were not + *) Bugfix: the proxy_set_x_var and fastcgi_set_var directives were not inherited. - *) Bugfix: in a redirect rewrite directive arguments were concatenated + *) Bugfix: in a redirect rewrite directive arguments were concatenated with URI by an "&" rather than a "?". - *) Bugfix: the lines without trailing ";" in the file being included by + *) Bugfix: the lines without trailing ";" in the file being included by the ngx_http_geo_module were silently ignored. *) Feature: the ngx_http_stub_status_module. - *) Bugfix: the unknown log format in the access_log directive caused - the segmentation fault. - - *) Feature: the new "document_root" parameter of the fastcgi_params + *) Bugfix: the unknown log format in the access_log directive caused the + segmentation fault. + + *) Feature: the new "document_root" parameter of the fastcgi_params directive. *) Feature: the fastcgi_redirect_errors directive. - *) Feature: the new "break" modifier of the "rewrite" directive allows - to stop the rewrite/location cycle and sets the current - configuration to the request. + *) Feature: the new "break" modifier of the "rewrite" directive allows + to stop the rewrite/location cycle and sets the current configuration + to the request. Changes with nginx 0.1.17 03 Feb 2005 - *) Change: the ngx_http_rewrite_module was rewritten from the scratch. - Now it is possible to redirect, to return the error codes, to check - the variables and referrers. The directives can be used inside + *) Change: the ngx_http_rewrite_module was rewritten from the scratch. + Now it is possible to redirect, to return the error codes, to check + the variables and referrers. The directives can be used inside locations. The redirect directive was canceled. *) Feature: the ngx_http_geo_module. *) Feature: the proxy_set_x_var and fastcgi_set_var directives. - *) Bugfix: the location configuration with "=" modifier may be used in + *) Bugfix: the location configuration with "=" modifier may be used in another location. - *) Bugfix: the correct content type was set only for requests that use + *) Bugfix: the correct content type was set only for requests that use small caps letters in extension. - *) Bugfix: if the proxy_pass or fastcgi_pass directives were set in the - location, and access was denied, and the error was redirected to a + *) Bugfix: if the proxy_pass or fastcgi_pass directives were set in the + location, and access was denied, and the error was redirected to a static page, then the segmentation fault occurred. - *) Bugfix: if in a proxied "Location" header was a relative URL, then a - host name and a slash were added to them; the bug had appeared in + *) Bugfix: if in a proxied "Location" header was a relative URL, then a + host name and a slash were added to them; the bug had appeared in 0.1.14. *) Bugfix: the system error message was not logged on Linux. @@ -5122,82 +5123,82 @@ Changes with nginx 0.1.17 Changes with nginx 0.1.16 25 Jan 2005 - *) Bugfix: if the response were transferred by chunks, then on the HEAD + *) Bugfix: if the response were transferred by chunks, then on the HEAD request the final chunk was issued. - *) Bugfix: the "Connection: keep-alive" header were issued, even if the + *) Bugfix: the "Connection: keep-alive" header were issued, even if the keepalive_timeout directive forbade the keep-alive use. - *) Bugfix: the errors in the ngx_http_fastcgi_module caused the + *) Bugfix: the errors in the ngx_http_fastcgi_module caused the segmentation faults. - *) Bugfix: the compressed response encrypted by SSL may not transferred + *) Bugfix: the compressed response encrypted by SSL may not transferred complete. - *) Bugfix: the TCP-specific TCP_NODELAY, TCP_NOPSUH, and TCP_CORK + *) Bugfix: the TCP-specific TCP_NODELAY, TCP_NOPSUH, and TCP_CORK options, are not used for the unix domain sockets. *) Feature: the rewrite directive supports the arguments rewriting. - *) Bugfix: the response code 400 was returned for the POST request with + *) Bugfix: the response code 400 was returned for the POST request with the "Content-Length: 0" header; the bug had appeared in 0.1.14. Changes with nginx 0.1.15 19 Jan 2005 - *) Bugfix: the error while the connecting to the FastCGI server caused + *) Bugfix: the error while the connecting to the FastCGI server caused segmentation fault. - *) Bugfix: the correct handling of the regular expression, that has + *) Bugfix: the correct handling of the regular expression, that has different number of the captures and substitutions. - *) Feature: the location, that is passed to the FastCGI server, can be + *) Feature: the location, that is passed to the FastCGI server, can be regular expression. - *) Bugfix: the FastCGI's parameter REQUEST_URI is now passed with the + *) Bugfix: the FastCGI's parameter REQUEST_URI is now passed with the arguments and in the original state. - *) Bugfix: the ngx_http_rewrite_module module was required to be built + *) Bugfix: the ngx_http_rewrite_module module was required to be built to use the regular expressions in locations. - *) Bugfix: the directive "proxy_preserve_host on" adds port 80 to the - "Host" headers, if upstream listen on port 80; the bug had appeared + *) Bugfix: the directive "proxy_preserve_host on" adds port 80 to the + "Host" headers, if upstream listen on port 80; the bug had appeared in 0.1.14. - *) Bugfix: the same paths in autoconfiguration parameters - --http-client-body-temp-path=PATH and --http-proxy-temp-path=PATH, - or --http-client-body-temp-path=PATH and - --http-fastcgi-temp-path=PATH caused segmentation fault. + *) Bugfix: the same paths in autoconfiguration parameters + --http-client-body-temp-path=PATH and --http-proxy-temp-path=PATH, or + --http-client-body-temp-path=PATH and --http-fastcgi-temp-path=PATH + caused segmentation fault. Changes with nginx 0.1.14 18 Jan 2005 - *) Feature: the autoconfiguration directives: - --http-client-body-temp-path=PATH, --http-proxy-temp-path=PATH, and + *) Feature: the autoconfiguration directives: + --http-client-body-temp-path=PATH, --http-proxy-temp-path=PATH, and --http-fastcgi-temp-path=PATH - *) Change: the directory name for the temporary files with the client - request body is specified by directive client_body_temp_path, by + *) Change: the directory name for the temporary files with the client + request body is specified by directive client_body_temp_path, by default it is <prefix>/client_body_temp. - *) Feature: the ngx_http_fastcgi_module and the directives: - fastcgi_pass, fastcgi_root, fastcgi_index, fastcgi_params, - fastcgi_connect_timeout, fastcgi_send_timeout, fastcgi_read_timeout, - fastcgi_send_lowat, fastcgi_header_buffer_size, fastcgi_buffers, - fastcgi_busy_buffers_size, fastcgi_temp_path, - fastcgi_max_temp_file_size, fastcgi_temp_file_write_size, + *) Feature: the ngx_http_fastcgi_module and the directives: + fastcgi_pass, fastcgi_root, fastcgi_index, fastcgi_params, + fastcgi_connect_timeout, fastcgi_send_timeout, fastcgi_read_timeout, + fastcgi_send_lowat, fastcgi_header_buffer_size, fastcgi_buffers, + fastcgi_busy_buffers_size, fastcgi_temp_path, + fastcgi_max_temp_file_size, fastcgi_temp_file_write_size, fastcgi_next_upstream, and fastcgi_x_powered_by. - *) Bugfix: the "[alert] zero size buf" error; the bug had appeared in + *) Bugfix: the "[alert] zero size buf" error; the bug had appeared in 0.1.3. - *) Change: the URI must be specified after the host name in the + *) Change: the URI must be specified after the host name in the proxy_pass directive. - *) Change: the %3F symbol in the URI was considered as the argument + *) Change: the %3F symbol in the URI was considered as the argument string start. - *) Feature: the unix domain sockets support in the + *) Feature: the unix domain sockets support in the ngx_http_proxy_module. *) Feature: the ssl_engine and ssl_ciphers directives. @@ -5206,13 +5207,13 @@ Changes with nginx 0.1.14 Changes with nginx 0.1.13 21 Dec 2004 - *) Feature: the server_names_hash and server_names_hash_threshold + *) Feature: the server_names_hash and server_names_hash_threshold directives. - *) Bugfix: the *.domain.tld names in the "server_name" directive did - not work. - - *) Bugfix: the %request_length log parameter logged the incorrect + *) Bugfix: the *.domain.tld names in the "server_name" directive did not + work. + + *) Bugfix: the %request_length log parameter logged the incorrect length. @@ -5220,12 +5221,12 @@ Changes with nginx 0.1.12 *) Feature: the %request_length log parameter. - *) Bugfix: when using the /dev/poll, select and poll on the platforms, - where these methods may do the false reports, there may be the long - delay when the request was passed via the keep-alive connection. It + *) Bugfix: when using the /dev/poll, select and poll on the platforms, + where these methods may do the false reports, there may be the long + delay when the request was passed via the keep-alive connection. It may be at least on Solaris when using the /dev/poll. - *) Bugfix: the send_lowat directive is ignored on Linux because Linux + *) Bugfix: the send_lowat directive is ignored on Linux because Linux does not support the SO_SNDLOWAT option. @@ -5233,26 +5234,26 @@ Changes with nginx 0.1.11 *) Feature: the worker_priority directive. - *) Change: both tcp_nopush and tcp_nodelay directives affect the + *) Change: both tcp_nopush and tcp_nodelay directives affect the transferred response. *) Bugfix: nginx did not call initgroups(). Thanks to Andrew Sitnikov and Andrei Nigmatulin. - *) Change: now the ngx_http_autoindex_module shows the file size in the + *) Change: now the ngx_http_autoindex_module shows the file size in the bytes. - *) Bugfix: the ngx_http_autoindex_module returned the 500 error if the + *) Bugfix: the ngx_http_autoindex_module returned the 500 error if the broken symlink was in a directory. - *) Bugfix: the files bigger than 4G could not be transferred using + *) Bugfix: the files bigger than 4G could not be transferred using sendfile. - *) Bugfix: if the backend was resolved to several backends and there - was an error while the response waiting then process may got caught - in an endless loop. - - *) Bugfix: the worker process may exit with the "unknown cycle" message + *) Bugfix: if the backend was resolved to several backends and there was + an error while the response waiting then process may got caught in an + endless loop. + + *) Bugfix: the worker process may exit with the "unknown cycle" message when the /dev/poll method was used. *) Bugfix: "close() channel failed" errors. @@ -5261,44 +5262,43 @@ Changes with nginx 0.1.11 *) Bugfix: the send_lowat directive did not work on Linux. - *) Bugfix: the segmentation fault occurred if there was no events + *) Bugfix: the segmentation fault occurred if there was no events section in configuration. *) Bugfix: nginx could not be built on OpenBSD. - *) Bugfix: the double slashes in "://" in the URI were converted to + *) Bugfix: the double slashes in "://" in the URI were converted to ":/". Changes with nginx 0.1.10 26 Nov 2004 - *) Bugfix: if the request without arguments contains "//", "/./", - "/../" or "%XX" then the last character in the request line was - lost; the bug had appeared in 0.1.9. - - *) Bugfix: the fix in 0.1.9 for the files bigger than 2G on Linux did + *) Bugfix: if the request without arguments contains "//", "/./", "/../" + or "%XX" then the last character in the request line was lost; the + bug had appeared in 0.1.9. + + *) Bugfix: the fix in 0.1.9 for the files bigger than 2G on Linux did not work. Changes with nginx 0.1.9 25 Nov 2004 - *) Bugfix: the proxied request was sent without arguments if the - request contains "//", "/./", "/../" or "%XX". - - *) Bugfix: the large compressed responses may be transferred not + *) Bugfix: the proxied request was sent without arguments if the request + contains "//", "/./", "/../" or "%XX". + + *) Bugfix: the large compressed responses may be transferred not completely. - *) Bugfix: the files bigger than 2G was not transferred on Linux that + *) Bugfix: the files bigger than 2G was not transferred on Linux that does not support sendfile64(). - *) Bugfix: while the build configuration on Linux the - --with-poll_module parameter was required; the bug had appeared in - 0.1.8. + *) Bugfix: while the build configuration on Linux the --with-poll_module + parameter was required; the bug had appeared in 0.1.8. Changes with nginx 0.1.8 20 Nov 2004 - *) Bugfix: in the ngx_http_autoindex_module if the long file names were + *) Bugfix: in the ngx_http_autoindex_module if the long file names were in the listing. *) Feature: the "^~" modifier in the location directive. @@ -5308,34 +5308,34 @@ Changes with nginx 0.1.8 Changes with nginx 0.1.7 12 Nov 2004 - *) Bugfix: on FreeBSD the segmentation fault may occur if the size of + *) Bugfix: on FreeBSD the segmentation fault may occur if the size of the transferred file was changed; the bug had appeared in 0.1.5. Changes with nginx 0.1.6 11 Nov 2004 - *) Bugfix: some location directive combinations with the regular + *) Bugfix: some location directive combinations with the regular expressions caused the wrong configuration choose. Changes with nginx 0.1.5 11 Nov 2004 - *) Bugfix: on Solaris and Linux there may be too many "recvmsg() + *) Bugfix: on Solaris and Linux there may be too many "recvmsg() returned not enough data" alerts. - *) Bugfix: there were the "writev() failed (22: Invalid argument)" - errors on Solaris in proxy mode without sendfile. On other platforms - that do not support sendfile at all the process got caught in an + *) Bugfix: there were the "writev() failed (22: Invalid argument)" + errors on Solaris in proxy mode without sendfile. On other platforms + that do not support sendfile at all the process got caught in an endless loop. - *) Bugfix: segmentation fault on Solaris in proxy mode and using + *) Bugfix: segmentation fault on Solaris in proxy mode and using sendfile. *) Bugfix: segmentation fault on Solaris. *) Bugfix: on-line upgrade did not work on Linux. - *) Bugfix: the ngx_http_autoindex_module module did not escape the + *) Bugfix: the ngx_http_autoindex_module module did not escape the spaces, the quotes, and the percent signs in the directory listing. *) Change: the decrease of the copy operations. @@ -5354,31 +5354,31 @@ Changes with nginx 0.1.3 *) Feature: the proxy_set_x_url directive. - *) Bugfix: proxy module may get caught in an endless loop when sendfile + *) Bugfix: proxy module may get caught in an endless loop when sendfile is not used. Changes with nginx 0.1.2 21 Oct 2004 - *) Feature: the --user=USER, --group=GROUP, and --with-ld-opt=OPTIONS + *) Feature: the --user=USER, --group=GROUP, and --with-ld-opt=OPTIONS options in configure. *) Feature: the server_name directive supports *.domain.tld. *) Bugfix: the portability improvements. - *) Bugfix: if configuration file was set in command line, the + *) Bugfix: if configuration file was set in command line, the reconfiguration was impossible; the bug had appeared in 0.1.1. - *) Bugfix: proxy module may get caught in an endless loop when sendfile + *) Bugfix: proxy module may get caught in an endless loop when sendfile is not used. - *) Bugfix: with sendfile the response was not recoded according to the + *) Bugfix: with sendfile the response was not recoded according to the charset module directives; the bug had appeared in 0.1.1. *) Bugfix: very seldom bug in the kqueue processing. - *) Bugfix: the gzip module compressed the proxied responses that was + *) Bugfix: the gzip module compressed the proxied responses that was already compressed. @@ -5388,24 +5388,24 @@ Changes with nginx 0.1.1 *) Feature: the tcp_nodelay directive. - *) Feature: the send_lowat directive is working not only on OSes that + *) Feature: the send_lowat directive is working not only on OSes that support kqueue NOTE_LOWAT, but also on OSes that support SO_SNDLOWAT. *) Feature: the setproctitle() emulation for Linux and Solaris. *) Bugfix: the "Location" header rewrite bug fixed while the proxying. - *) Bugfix: the ngx_http_chunked_module module may get caught in an + *) Bugfix: the ngx_http_chunked_module module may get caught in an endless loop. *) Bugfix: the /dev/poll module bugs fixed. - *) Bugfix: the responses were corrupted when the temporary files were + *) Bugfix: the responses were corrupted when the temporary files were used while the proxying. *) Bugfix: the unescaped requests were passed to the backend. - *) Bugfix: while the build configuration on Linux 2.4 the + *) Bugfix: while the build configuration on Linux 2.4 the --with-poll_module parameter was required.