Mercurial > hg > nginx
changeset 2114:5cbd114a2b1d stable-0.5 release-0.5.37
nginx-0.5.37-RELEASE
author | Igor Sysoev <igor@sysoev.ru> |
---|---|
date | Mon, 07 Jul 2008 12:09:02 +0000 |
parents | e94149d5de37 |
children | d334dd0fb436 |
files | docs/xml/nginx/changes.xml |
diffstat | 1 files changed, 188 insertions(+), 115 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/xml/nginx/changes.xml Mon Jul 07 12:01:35 2008 +0000 +++ b/docs/xml/nginx/changes.xml Mon Jul 07 12:09:02 2008 +0000 @@ -9,6 +9,74 @@ <title lang="en">nginx changelog</title> +<changes ver="0.5.37" date="07.07.2008"> + +<change type="bugfix"> +<para lang="ru"> +при совместном использовании sub_filter и SSI +ответы могли передаваться неверно. +</para> +<para lang="en"> +if sub_filter and SSI were used together, then responses might +were transferred incorrectly. +</para> +</change> + +<change type="bugfix"> +<para lang="ru"> +большие включения в SSI могли передавались не полностью. +</para> +<para lang="en"> +large SSI inclusions might be truncated. +</para> +</change> + +<change type="bugfix"> +<para lang="ru"> +рабочие процессы могли не реагировать на сигналы переконфигурации +и ротации логов. +</para> +<para lang="en"> +worker processes might not catch reconfiguration and log rotation signals. +</para> +</change> + +<change type="bugfix"> +<para lang="ru"> +nginx не собирался на последних Fedora 9 Linux.<br/> +Спасибо Roxis. +</para> +<para lang="en"> +nginx could not be built on latest Fedora 9 Linux.<br/> +Thanks to Roxis. +</para> +</change> + +<change type="bugfix"> +<para lang="ru"> +при использовании keepalive на Linux +в рабочем процессе мог произойти segmentation fault. +</para> +<para lang="en"> +a segmentation fault might occur in worker process on Linux, +if keepalive was enabled. +</para> +</change> + +<change type="bugfix"> +<para lang="ru"> +во время переконфигурации на некоторых 64-битном платформах в лог +записывался alert "sendmsg() failed (9: Bad file descriptor)". +</para> +<para lang="en"> +an alert "sendmsg() failed (9: Bad file descriptor)" on some 64-bit platforms +while reconfiguration. +</para> +</change> + +</changes> + + <changes ver="0.5.36" date="04.05.2008"> <change type="bugfix"> @@ -48,7 +116,7 @@ </para> <para lang="en"> nginx issued the bogus error message "SSL_shutdown() failed (SSL: )"; -bug appeared in 0.5.35. +the bug had appeared in 0.5.35. </para> </change> @@ -59,7 +127,7 @@ </para> <para lang="en"> in HTTPS mode requests might fail with the "bad write retry" error; -bug appeared in 0.5.35. +the bug had appeared in 0.5.35. </para> </change> @@ -86,7 +154,7 @@ <para lang="en"> a segmentation fault occurred in master process if the "fastcgi_catch_stderr" directive was used; -bug appeared in 0.5.32.<br/> +the bug had appeared in 0.5.32.<br/> Thanks to Manlio Perillo. </para> </change> @@ -136,7 +204,7 @@ </para> <para lang="en"> in HTTPS mode requests might fail with the "bad write retry" error; -bug appeared in 0.5.13. +the bug had appeared in 0.5.13. </para> </change> @@ -194,7 +262,7 @@ <para lang="en"> if the "?" character was in a "error_page" directive, then it was escaped in a proxied request; -bug appeared in 0.5.32. +the bug had appeared in 0.5.32. </para> </change> @@ -293,7 +361,7 @@ </para> <para lang="en"> URL double escaping in a redirect of the "msie_refresh" directive; -bug appeared in 0.5.28. +the bug had appeared in 0.5.28. </para> </change> @@ -511,7 +579,7 @@ <para lang="en"> nginx supported low case only "close" and "keep-alive" values in the "Connection" request header line; -bug appeared in 0.5.32. +the bug had appeared in 0.5.32. </para> </change> @@ -748,7 +816,7 @@ <para lang="en"> the "proxy_ignore_client_abort" and "fastcgi_ignore_client_abort" directives did not work; -bug appeared in 0.5.13. +the bug had appeared in 0.5.13. </para> </change> @@ -856,7 +924,7 @@ </para> <para lang="en"> fix building on Solaris/amd64 by Sun Studio 11 and early versions; -bug appeared in 0.5.29. +the bug had appeared in 0.5.29. </para> </change> @@ -1003,6 +1071,7 @@ </changes> +<!-- 0.6.x branch --> <changes ver="0.5.25" date="11.06.2007"> <change type="bugfix"> @@ -1012,7 +1081,7 @@ </para> <para lang="en"> nginx could not be built with the --without-http_rewrite_module parameter; -bug appeared in 0.5.24. +the bug had appeared in 0.5.24. </para> </change> @@ -1039,7 +1108,7 @@ </para> <para lang="en"> a part of response body might be passed uncompressed if gzip was used; -bug appeared in 0.5.23. +the bug had appeared in 0.5.23. </para> </change> @@ -1113,7 +1182,7 @@ </para> <para lang="en"> a big request body might not be passed to backend; -bug appeared in 0.5.21. +the bug had appeared in 0.5.21. </para> </change> @@ -1350,7 +1419,7 @@ after first reconfiguration and receiving any signal if nginx was built with ngx_http_perl_module and perl did not support multiplicity; -bug appeared in 0.5.9. +the bug had appeared in 0.5.9. </para> </change> @@ -1363,7 +1432,7 @@ <para lang="en"> if perl did not support multiplicity, then after reconfiguration perl code did not work; -bug appeared in 0.3.38. +the bug had appeared in 0.3.38. </para> </change> @@ -1449,7 +1518,7 @@ a segmentation fault might occur in worker process if a charset was set in the "Content-Type" header line and the line has trailing ";"; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -1471,7 +1540,7 @@ </para> <para lang="en"> nginx could not be built on Solaris without the --with-debug option; -bug appeared in 0.5.15. +the bug had appeared in 0.5.15. </para> </change> @@ -1648,8 +1717,9 @@ ошибка появилась в 0.5.8. </para> <para lang="en"> -nginx could not be built on platforms different from i386, amd64, sparc and ppc; -bug appeared in 0.5.8. +nginx could not be built on platforms different from i386, amd64, sparc, +and ppc; +the bug had appeared in 0.5.8. </para> </change> @@ -1664,8 +1734,9 @@ ошибка появилась в 0.5.8. </para> <para lang="en"> -nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.5.8. +nginx could not be built on platforms different from i386, amd64, sparc, +and ppc; +the bug had appeared in 0.5.8. </para> </change> @@ -1678,7 +1749,7 @@ <para lang="en"> a segmentation fault might occur in worker process if the temporarily files were used while working with FastCGI server; -bug appeared in 0.5.8. +the bug had appeared in 0.5.8. </para> </change> @@ -1725,7 +1796,7 @@ </para> <para lang="en"> the response was incorrect if several ranges were requested; -bug appeared in 0.5.6. +the bug had appeared in 0.5.6. </para> </change> @@ -1777,7 +1848,7 @@ <para lang="en"> while online executable file upgrade the new master process did not inherit the listening sockets; -bug appeared in 0.5.9. +the bug had appeared in 0.5.9. </para> </change> @@ -1790,7 +1861,7 @@ <para lang="en"> a segmentation fault might occur in worker process if nginx was built with -O2 optimization; -bug appeared in 0.5.1. +the bug had appeared in 0.5.1. </para> </change> @@ -1909,7 +1980,7 @@ <para lang="en"> if the "proxy_buffering off" directive was used and a client connection was non-active, then the connection was closed after send timeout; -bug appeared in 0.4.7. +the bug had appeared in 0.4.7. </para> </change> @@ -2176,7 +2247,7 @@ </para> <para lang="en"> a segmentation fault might occur if the $host variable was used; -bug appeared in 0.4.14. +the bug had appeared in 0.4.14. </para> </change> @@ -2229,7 +2300,7 @@ <para lang="en"> if the "proxy_pass" directive used the name of the "upstream" block, then nginx tried to resolve the name; -bug appeared in 0.5.1. +the bug had appeared in 0.5.1. </para> </change> @@ -2256,7 +2327,7 @@ </para> <para lang="en"> for Eudora for Mac; -bug appeared in 0.4.11.<br/> +the bug had appeared in 0.4.11.<br/> Thanks to Bron Gondwana. </para> </change> @@ -2270,7 +2341,7 @@ <para lang="en"> if the "upstream" name was used in the "fastcgi_pass", then the message "no port in upstream" was issued; -bug appeared in 0.5.0. +the bug had appeared in 0.5.0. </para> </change> @@ -2284,7 +2355,7 @@ <para lang="en"> if the "proxy_pass" and "fastcgi_pass" directives used the same servers but different ports, then these directives uses the first described port; -bug appeared in 0.5.0. +the bug had appeared in 0.5.0. </para> </change> @@ -2297,7 +2368,7 @@ <para lang="en"> if the "proxy_pass" and "fastcgi_pass" directives used the unix domain sockets, then these directives used first described socket; -bug appeared in 0.5.0. +the bug had appeared in 0.5.0. </para> </change> @@ -2393,7 +2464,7 @@ </para> <para lang="en"> nginx could not be built on 64-bit platforms; -bug appeared in 0.4.14. +the bug had appeared in 0.4.14. </para> </change> @@ -2427,7 +2498,7 @@ </para> <para lang="en"> ngx_http_perl_module did not work with perl built with the threads support; -bug appeared in 0.3.38. +the bug had appeared in 0.3.38. </para> </change> @@ -2545,7 +2616,7 @@ </para> <para lang="en"> a charset could not be set for ngx_http_autoindex_module responses; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -2576,7 +2647,7 @@ </para> <para lang="en"> the 50th subrequest in SSI response did not work; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -2646,7 +2717,7 @@ <para lang="en"> if the APOP was enabled in the POP3 proxy, then the USER/PASS commands might not work; -bug appeared in 0.4.10. +the bug had appeared in 0.4.10. </para> </change> @@ -2693,7 +2764,7 @@ </para> <para lang="en"> the ngx_http_flv_module did not support the byte ranges for full responses; -bug appeared in 0.4.7. +the bug had appeared in 0.4.7. </para> </change> @@ -2704,7 +2775,7 @@ </para> <para lang="en"> nginx could not be built on Debian amd64; -bug appeared in 0.4.9. +the bug had appeared in 0.4.9. </para> </change> @@ -2857,7 +2928,7 @@ <para lang="en"> after redirecting error by an "error_page" directive any ngx_http_rewrite_module directive returned this error code; -bug appeared in 0.4.4. +the bug had appeared in 0.4.4. </para> </change> @@ -2873,7 +2944,7 @@ </para> <para lang="en"> nginx could not be built on Linux and Solaris; -bug appeared in 0.4.4. +the bug had appeared in 0.4.4. </para> </change> @@ -2995,7 +3066,7 @@ <para lang="en"> a segmentation fault occurred if an unix domain socket was used in a "proxy_pass" directive; -bug appeared in 0.3.47. +the bug had appeared in 0.3.47. </para> </change> @@ -3030,7 +3101,7 @@ </para> <para lang="en"> the O_NOATIME flag support on Linux was canceled; -bug appeared in 0.4.1. +the bug had appeared in 0.4.1. </para> </change> @@ -3135,7 +3206,7 @@ <para lang="en"> a segmentation fault occurred if there was an "index" directive with variables and the first index name was without variables; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -3195,7 +3266,7 @@ <para lang="en"> a worker process may got caught in an endless loop while an error redirection; -bug appeared in 0.3.59. +the bug had appeared in 0.3.59. </para> </change> @@ -3231,7 +3302,7 @@ <para lang="en"> the "error_page" directive did not changes the "Content-Type" header line after the "X-Accel-Redirect" was used; -bug appeared in 0.3.58. +the bug had appeared in 0.3.58. </para> </change> @@ -3465,7 +3536,7 @@ <para lang="en"> on some condition while reconfiguration character codes inside the "charset_map" may be treated invalid; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -3532,7 +3603,7 @@ </para> <para lang="en"> nginx could not be built on amd64 platform; -bug appeared in 0.3.53. +the bug had appeared in 0.3.53. </para> </change> @@ -3632,7 +3703,7 @@ </para> <para lang="en"> the worker process may got caught in an endless loop if the limit rate was used; -bug appeared in 0.3.37. +the bug had appeared in 0.3.37. </para> </change> @@ -3645,7 +3716,7 @@ <para lang="en"> ngx_http_charset_module logged "unknown charset" alert, even if the recoding was not needed; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -3672,7 +3743,7 @@ </para> <para lang="en"> the "<" symbols might disappeared some conditions in the SSI; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. </para> </change> @@ -3816,7 +3887,7 @@ 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; -bug appeared in 0.3.42. +the bug had appeared in 0.3.42. </para> </change> @@ -3828,7 +3899,7 @@ <para lang="en"> the ngx_http_perl_module could not be built, if the perl was built with the threads support; -bug appeared in 0.3.46. +the bug had appeared in 0.3.46. </para> </change> @@ -3940,7 +4011,7 @@ в таблицу перекодировки koi-win добавлены символы евро и номера. </para> <para lang="en"> -the euro и N symbols were added to koi-win conversion table. +the euro and N symbols were added to koi-win conversion table. </para> </change> @@ -4175,7 +4246,7 @@ <para lang="en"> the active connection counter increased on the exceeding of the connection limit specified by the "worker_connections" directive; -bug appeared in 0.2.0. +the bug had appeared in 0.2.0. </para> </change> @@ -4186,7 +4257,7 @@ </para> <para lang="en"> the limit rate might not work on some condition; -bug appeared in 0.3.38. +the bug had appeared in 0.3.38. </para> </change> @@ -4422,7 +4493,7 @@ <para lang="en"> the accept-filter and the TCP_DEFER_ACCEPT option were set for first "listen" directive only; -bug appeared in 0.3.31. +the bug had appeared in 0.3.31. </para> </change> @@ -4496,7 +4567,7 @@ </para> <para lang="en"> the debug logging on startup and reconfiguration time was removed; -bug appeared in 0.3.31. +the bug had appeared in 0.3.31. </para> </change> @@ -4555,7 +4626,7 @@ if there were several "listen" directives listening one various addresses inside one server, then server names like "*.domain.tld" worked for first address only; -bug appeared in 0.3.18. +the bug had appeared in 0.3.18. </para> </change> @@ -4610,7 +4681,7 @@ </para> <para lang="en"> nginx could not be built on i386 platform, if the PIC was used; -bug appeared in 0.3.27. +the bug had appeared in 0.3.27. </para> </change> @@ -4843,7 +4914,7 @@ <para lang="en"> the segmentation fault was occurred on start or while reconfiguration if there was invalid configuration; -bug appeared in 0.3.24. +the bug had appeared in 0.3.24. </para> </change> @@ -4898,7 +4969,7 @@ <para lang="en"> on 64-bit platforms segmentation fault may occurred on start if the many names were used in the "server_name" directives; -bug appeared in 0.3.18. +the bug had appeared in 0.3.18. </para> </change> @@ -4966,7 +5037,7 @@ <para lang="en"> segmentation fault was occurred if the "none" or "blocked" values was specified in the "valid_referers" directive; -bug appeared in 0.3.18. +the bug had appeared in 0.3.18. </para> </change> @@ -5127,7 +5198,7 @@ </para> <para lang="en"> segmentation fault was occurred if configuration file did not exist; -bug appeared in 0.3.12. +the bug had appeared in 0.3.12. </para> </change> @@ -5138,7 +5209,7 @@ </para> <para lang="en"> on 64-bit platforms segmentation fault may occurred on start; -bug appeared in 0.3.16. +the bug had appeared in 0.3.16. </para> </change> @@ -5172,7 +5243,7 @@ </para> <para lang="en"> the timeouts were not used in SSL handshake; -bug appeared in 0.2.4. +the bug had appeared in 0.2.4. </para> </change> @@ -5267,7 +5338,7 @@ <para lang="en"> nginx did not close connection to IMAP/POP3 backend for the SSL connections; -bug appeared in 0.3.13.<br/> +the bug had appeared in 0.3.13.<br/> Thanks to Rob Mueller. </para> </change> @@ -5279,7 +5350,7 @@ </para> <para lang="en"> segmentation fault may occurred in at SSL shutdown; -bug appeared in 0.3.13. +the bug had appeared in 0.3.13. </para> </change> @@ -5329,7 +5400,7 @@ </para> <para lang="en"> in the 304 response the body was transferred; -bug appeared in 0.3.13. +the bug had appeared in 0.3.13. </para> </change> @@ -5383,7 +5454,7 @@ </para> <para lang="en"> the "auth_basic" directive did not disable the authorization; -bug appeared in 0.3.11. +the bug had appeared in 0.3.11. </para> </change> @@ -5450,7 +5521,7 @@ </para> <para lang="en"> the changes in accept mutex handling when the "rtsig" method was used; -bug appeared in 0.3.0. +the bug had appeared in 0.3.0. </para> </change> @@ -5486,7 +5557,7 @@ <para lang="en"> if the "combined" format was explicitly specified in the "access_log" directive, then the empty lines was written to the log; -bug appeared in 0.3.8. +the bug had appeared in 0.3.8. </para> </change> @@ -5522,7 +5593,7 @@ </para> <para lang="en"> nginx did not pass the client request headers and body while proxying; -bug appeared in 0.3.10. +the bug had appeared in 0.3.10. </para> </change> @@ -5658,7 +5729,7 @@ </para> <para lang="en"> nginx considered URI as unsafe if two any symbols was between two slashes; -bug appeared in 0.3.8. +the bug had appeared in 0.3.8. </para> </change> @@ -5792,7 +5863,7 @@ 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; -bug appeared in 0.2.6. +the bug had appeared in 0.2.6. </para> </change> @@ -5856,8 +5927,9 @@ ошибка появилась в 0.3.2. </para> <para lang="en"> -nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.3.2. +nginx could not be built on platforms different from i386, amd64, sparc, +and ppc; +the bug had appeared in 0.3.2. </para> </change> @@ -5893,7 +5965,7 @@ <para lang="en"> if at least in one server was no the "listen" directive, then nginx did not listen on the 80 port; -bug appeared in 0.3.3. +the bug had appeared in 0.3.3. </para> </change> @@ -5921,7 +5993,7 @@ <para lang="en"> the segmentation fault may occurred if the IMAP/POP3 login was changed by authorization server; -bug appeared in 0.2.2. +the bug had appeared in 0.2.2. </para> </change> @@ -5932,7 +6004,7 @@ </para> <para lang="en"> the accept mutex did not work and all connections were handled by one process; -bug appeared in 0.3.3. +the bug had appeared in 0.3.3. </para> </change> @@ -5959,7 +6031,7 @@ </para> <para lang="en"> nginx could not be built on Linux 2.4+ and MacOS X; -bug appeared in 0.3.3. +the bug had appeared in 0.3.3. </para> </change> @@ -6028,7 +6100,7 @@ <para lang="en"> the mime type may be incorrectly set to default value for index file with variable in the name; -bug appeared in 0.3.0. +the bug had appeared in 0.3.0. </para> </change> @@ -6138,7 +6210,7 @@ <para lang="en"> the segmentation fault occurred when the signal queue overflowed if the "rtsig" method was used; -bug appeared in 0.2.0. +the bug had appeared in 0.2.0. </para> </change> @@ -6238,7 +6310,7 @@ 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; -bug appeared in 0.2.2. +the bug had appeared in 0.2.2. </para> </change> @@ -6312,7 +6384,7 @@ </para> <para lang="en"> in proxying location without trailing slash; -bug appeared in 0.1.44. +the bug had appeared in 0.1.44. </para> </change> @@ -6323,7 +6395,7 @@ </para> <para lang="en"> the segmentation fault may occurred if the "rtsig" method was used; -bug appeared in 0.2.0. +the bug had appeared in 0.2.0. </para> </change> @@ -6339,7 +6411,7 @@ </para> <para lang="en"> nginx could not be built without the --with-debug option; -bug appeared in 0.2.2. +the bug had appeared in 0.2.2. </para> </change> @@ -6431,7 +6503,7 @@ <para lang="en"> if all backend using in load-balancing failed after one error, then nginx may got caught in an endless loop; -bug appeared in 0.2.0. +the bug had appeared in 0.2.0. </para> </change> @@ -6691,7 +6763,7 @@ <para lang="en"> the segmentation fault may occurred if there were errors while working with proxied or FastCGI server; -in the proxied mode the bug appeared in 0.1.29. +in the proxied mode the the bug had appeared in 0.1.29. </para> </change> @@ -6708,7 +6780,7 @@ 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 bug appeared in 0.1.29. +in the proxied mode the the bug had appeared in 0.1.29. </para> </change> @@ -6737,7 +6809,7 @@ </para> <para lang="en"> the "limit_rate" directive did not work inside the "if" block; -bug appeared in 0.1.38. +the bug had appeared in 0.1.38. </para> </change> @@ -6781,7 +6853,7 @@ <para lang="en"> the "Set-Cookie" header line was not transferred when the "X-Accel-Redirect" was used; -bug appeared in 0.1.39. +the bug had appeared in 0.1.39. </para> </change> @@ -6856,7 +6928,7 @@ <para lang="en"> the ngx_http_proxy_module and ngx_http_fastcgi_module may close a connection before anything was transferred to a client; -bug appeared in 0.1.38. +the bug had appeared in 0.1.38. </para> </change> @@ -6889,7 +6961,7 @@ <para lang="en"> if the backend response had the "Location" header line and nginx should not rewrite this line, then the 500 code response body was transferred; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -6902,7 +6974,7 @@ <para lang="en"> some directives of the ngx_http_proxy_module and ngx_http_fastcgi_module were not inherited from the server to the location level; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -6922,7 +6994,7 @@ </para> <para lang="en"> the ngx_http_autoindex_module did not show correctly the long file names; -bug appeared in 0.1.38. +the bug had appeared in 0.1.38. </para> </change> @@ -7018,7 +7090,7 @@ <para lang="en"> nginx treated the backend response as invalid if the status line in the header was transferred in two packets; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -7201,7 +7273,7 @@ <para lang="en"> the segmentation fault was occurred if the backend response header was in several packets; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -7237,7 +7309,7 @@ <para lang="en"> nginx returned the 400 response on requests like <nobr>"GET http://www.domain.com/uri HTTP/1.0"</nobr>; -bug appeared in 0.1.28. +the bug had appeared in 0.1.28. </para> </change> @@ -7296,7 +7368,7 @@ </para> <para lang="en"> nginx could not be built with the --without-pcre parameter; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -7343,7 +7415,7 @@ </para> <para lang="en"> the arguments were omitted in the redirects, issued by the "rewrite" directive; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. </para> </change> @@ -7416,7 +7488,7 @@ </para> <para lang="en"> the redirect with the 301 code was transferred without response body; -bug appeared in 0.1.30. +the bug had appeared in 0.1.30. </para> </change> @@ -7452,7 +7524,7 @@ <para lang="en"> 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 bug appeared in 0.1.29 only. +in proxy mode the the bug had appeared in 0.1.29 only. </para> </change> @@ -7735,7 +7807,7 @@ <para lang="en"> the segmentation fault was occurred if the backend sent an invalid line in response header; -bug appeared in 0.1.26. +the bug had appeared in 0.1.26. </para> </change> @@ -8125,8 +8197,9 @@ ошибка появилась в 0.1.22. </para> <para lang="en"> -nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.1.22. +nginx could not be built on platforms different from i386, amd64, sparc, +and ppc; +the bug had appeared in 0.1.22. </para> </change> @@ -8176,7 +8249,7 @@ </para> <para lang="en"> the installation paths were incorrectly quoted on Linux and Solaris; -bug appeared in 0.1.21. +the bug had appeared in 0.1.21. </para> </change> @@ -8455,7 +8528,7 @@ <para lang="en"> if in a proxied "Location" header was a relative URL, then a host name and a slash were added to them; -bug appeared in 0.1.14. +the bug had appeared in 0.1.14. </para> </change> @@ -8541,7 +8614,7 @@ <para lang="en"> the response code 400 was returned for the POST request with the "Content-Length: 0" header; -bug appeared in 0.1.14. +the bug had appeared in 0.1.14. </para> </change> @@ -8614,7 +8687,7 @@ <para lang="en"> the directive <nobr>"proxy_preserve_host on"</nobr> adds port 80 to the "Host" headers, if upstream listen on port 80; -bug appeared in 0.1.14. +the bug had appeared in 0.1.14. </para> </change> @@ -8715,7 +8788,7 @@ </para> <para lang="en"> the "[alert] zero size buf" error; -bug appeared in 0.1.3. +the bug had appeared in 0.1.3. </para> </change> @@ -8984,7 +9057,7 @@ <para lang="en"> if the request without arguments contains "//", "/./", "/../" or "%XX" then the lost character in the request line was lost; -bug appeared in 0.1.9. +the bug had appeared in 0.1.9. </para> </change> @@ -9041,7 +9114,7 @@ <para lang="en"> while the build configuration on Linux the --with-poll_module parameter was required; -bug appeared in 0.1.8. +the bug had appeared in 0.1.8. </para> </change> @@ -9091,7 +9164,7 @@ <para lang="en"> on FreeBSD the segmentation fault may occur if the size of the transferred file was changed; -bug appeared in 0.1.5. +the bug had appeared in 0.1.5. </para> </change> @@ -9285,7 +9358,7 @@ <para lang="en"> if configuration file was set in command line, the reconfiguration was impossible; -bug appeared in 0.1.1. +the bug had appeared in 0.1.1. </para> </change> @@ -9308,7 +9381,7 @@ <para lang="en"> with sendfile the response was not recoded according to the charset module directives; -bug appeared in 0.1.1. +the bug had appeared in 0.1.1. </para> </change>