From 9f5e153185f0f201a0f640e582044a4557ca557f Mon Sep 17 00:00:00 2001 From: Igor Sysoev Date: Mon, 23 Jun 2008 10:34:57 +0000 Subject: [PATCH] nginx-0.7.3-RELEASE --- docs/xml/nginx/changes.xml | 315 +++++++++++++++++++++---------------- 1 file changed, 182 insertions(+), 133 deletions(-) diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml index 20c248598..ae1ef5c40 100644 --- a/docs/xml/nginx/changes.xml +++ b/docs/xml/nginx/changes.xml @@ -9,6 +9,55 @@ nginx changelog + + + + +MIME-тип для расширения rss изменён на "application/rss+xml". + + +the "rss" extension MIME type has been changed to "application/rss+xml". + + + + + +теперь директива "gzip_vary on" выдаёт строку +"Vary: Accept-Encoding" +в заголовке ответа и для несжатых ответов. + + +now the "gzip_vary" directive turned on issues +a "Vary: Accept-Encoding" +header line for uncompressed responses too. + + + + + +теперь при использовании протокола "https://" в директиве rewrite +автоматически делается редирект. + + +now the "rewrite" directive does a redirect automatically +if the "https://" protocol is used. + + + + + +директива proxy_pass не работала с протоколом HTTPS; +ошибка появилась в 0.6.9. + + +the "proxy_pass" directive did not work with the HTTPS protocol; +the bug had appeared in 0.6.9. + + + + + + @@ -49,7 +98,7 @@ Thanks to Manlio Perillo. after changing URI via a "rewrite" directive nginx did not search a new location; -bug appeared in 0.7.1.
+the bug had appeared in 0.7.1.
Thanks to Maxim Dounin. @@ -61,7 +110,7 @@ nginx nginx could not be built without PCRE library; -bug appeared in 0.7.1. +the bug had appeared in 0.7.1. @@ -237,7 +286,7 @@ nginx nginx did not process FastCGI response if header was at the end of FastCGI record; -bug appeared in 0.6.2.
+the bug had appeared in 0.6.2.
Thanks to Sergey Serov. @@ -325,7 +374,7 @@ nginx nginx could not be built on OpenBSD; -bug appeared in 0.6.15. +the bug had appeared in 0.6.15. @@ -350,7 +399,7 @@ the ngx_google_perftools_module. the ngx_http_perl_module could not be built on 64-bit platforms; -bug appeared in 0.6.27. +the bug had appeared in 0.6.27. @@ -366,7 +415,7 @@ bug appeared in 0.6.27. the rtsig method could not be built; -bug appeared in 0.6.27. +the bug had appeared in 0.6.27. @@ -608,7 +657,7 @@ nginx nginx issued the bogus error message "SSL_shutdown() failed (SSL: )"; -bug appeared in 0.6.23. +the bug had appeared in 0.6.23. @@ -619,7 +668,7 @@ bug appeared in 0.6.23. in HTTPS mode requests might fail with the "bad write retry" error; -bug appeared in 0.6.23. +the bug had appeared in 0.6.23. @@ -696,7 +745,7 @@ ngx_http_dav_module; the ngx_http_gzip_static_module did not allow the ngx_http_dav_module to work; -bug appeared in 0.6.23. +the bug had appeared in 0.6.23. @@ -718,7 +767,7 @@ nginx nginx could not be built without PCRE library; -bug appeared in 0.6.23. +the bug had appeared in 0.6.23. @@ -733,7 +782,7 @@ bug appeared in 0.6.23. a segmentation fault might occur in worker process if HTTPS was used; -bug appeared in 0.6.23. +the bug had appeared in 0.6.23. @@ -872,7 +921,7 @@ Thanks to Oleg Motienko. 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. @@ -904,7 +953,7 @@ allocated memory. 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; -bug appeared in 0.5.9.
+the bug had appeared in 0.5.9.
Thanks to Boris Zhmurov. @@ -951,7 +1000,7 @@ Thanks to Olexander Shtepa. the last address was missed in the $upstream_addr variable; -bug appeared in 0.6.18. +the bug had appeared in 0.6.18. @@ -978,7 +1027,7 @@ the "fastcgi_next_upstream invalid_header" directive. a segmentation fault occurred in master process if the "fastcgi_catch_stderr" directive was used; -bug appeared in 0.6.10.
+the bug had appeared in 0.6.10.
Thanks to Manlio Perillo. @@ -1009,7 +1058,7 @@ resolver a segmentation fault might occur in worker process if a "proxy_pass" directive with URI-part was used; -bug appeared in 0.6.19. +the bug had appeared in 0.6.19. @@ -1066,7 +1115,7 @@ then nginx returned usual response. a segmentation fault might occur in worker process if a "proxy_pass" directive with URI-part was used; -bug appeared in 0.6.19. +the bug had appeared in 0.6.19. @@ -1172,7 +1221,7 @@ Thanks to Alexander V. Inyukhin. URL double escaping in a redirect of the "msie_refresh" directive; -bug appeared in 0.6.4. +the bug had appeared in 0.6.4. @@ -1240,7 +1289,7 @@ Thanks to Ilya Novikov. if the "?" character was in a "error_page" directive, then it was escaped in a proxied request; -bug appeared in 0.6.11. +the bug had appeared in 0.6.11. @@ -1338,7 +1387,7 @@ error_page nginx if request with request body was redirected using the "error_page" directive, then nginx tried to read the request body again; -bug appeared in 0.6.7. +the bug had appeared in 0.6.7. @@ -1351,7 +1400,7 @@ bug appeared in 0.6.7. a segmentation fault occurred in worker process if no server_name was explicitly defined for server processing request; -bug appeared in 0.6.7. +the bug had appeared in 0.6.7. @@ -1397,7 +1446,7 @@ the "access_log" directive may be used inside the "limit_except" block. if all upstream servers were failed, then all servers had got weight the was equal one until servers became alive; -bug appeared in 0.6.6. +the bug had appeared in 0.6.6. @@ -1454,7 +1503,7 @@ nginx nginx supported low case only "close" and "keep-alive" values in the "Connection" request header line; -bug appeared in 0.6.11. +the bug had appeared in 0.6.11. @@ -1535,7 +1584,7 @@ wildcard the trailing wildcards did not work; -bug appeared in 0.6.9. +the bug had appeared in 0.6.9. @@ -1607,7 +1656,7 @@ nginx did not support several "Connection" request header lines. if the "max_fails" was set for upstream server, then after first failure server weight was always one; -bug appeared in 0.6.6. +the bug had appeared in 0.6.6. @@ -1633,7 +1682,7 @@ directives. socket leak; -bug appeared in 0.6.7. +the bug had appeared in 0.6.7. @@ -1672,7 +1721,7 @@ if /dev/poll method was used. a worker process may got caught in an endless loop, if the HTTPS protocol was used; -bug appeared in 0.6.7. +the bug had appeared in 0.6.7. @@ -1703,7 +1752,7 @@ nginx nginx could not be built on amd64; -bug appeared in 0.6.8. +the bug had appeared in 0.6.8. @@ -1754,7 +1803,7 @@ now nginx escapes "%" in $memcached_key variable. nginx used path relative to configuration prefix for non-absolute configuration file path specified in the "-c" key; -bug appeared in 0.6.6. +the bug had appeared in 0.6.6. @@ -1892,7 +1941,7 @@ Thanks to Jiang Hong. a worker process may got caught in an endless loop, if a "server" inside "upstream" block was marked as "down"; -bug appeared in 0.6.6. +the bug had appeared in 0.6.6. @@ -1986,7 +2035,7 @@ nginx fix building on Solaris/amd64 by Sun Studio 11 and early versions; -bug appeared in 0.6.4. +the bug had appeared in 0.6.4. @@ -2183,7 +2232,7 @@ if the eventport method was used. 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. @@ -2277,7 +2326,7 @@ nginx 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. @@ -2304,7 +2353,7 @@ using HTTP/0.9. 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. @@ -2378,7 +2427,7 @@ in the HTTPS protocol in the "proxy_pass" directive. a big request body might not be passed to backend; -bug appeared in 0.5.21. +the bug had appeared in 0.5.21. @@ -2615,7 +2664,7 @@ 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; -bug appeared in 0.5.9. +the bug had appeared in 0.5.9. @@ -2628,7 +2677,7 @@ bug appeared in 0.5.9. 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. @@ -2714,7 +2763,7 @@ Thanks to Pavel Yarkovoy. 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. @@ -2736,7 +2785,7 @@ nginx 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. @@ -2914,7 +2963,7 @@ nginx nginx could not be built on platforms different from i386, amd64, sparc and ppc; -bug appeared in 0.5.8. +the bug had appeared in 0.5.8. @@ -2930,7 +2979,7 @@ nginx nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.5.8. +the bug had appeared in 0.5.8. @@ -2943,7 +2992,7 @@ bug appeared in 0.5.8. 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. @@ -2990,7 +3039,7 @@ Thanks to Chris McGrath. the response was incorrect if several ranges were requested; -bug appeared in 0.5.6. +the bug had appeared in 0.5.6. @@ -3042,7 +3091,7 @@ if nginx was built with -O2 optimization. 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. @@ -3055,7 +3104,7 @@ segmentation fault; 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. @@ -3174,7 +3223,7 @@ send_timeout; 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. @@ -3441,7 +3490,7 @@ nginx might report about configuration error. 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. @@ -3494,7 +3543,7 @@ the $r->has_request_body method did not work. 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. @@ -3521,7 +3570,7 @@ of a request. for Eudora for Mac; -bug appeared in 0.4.11.
+the bug had appeared in 0.4.11.
Thanks to Bron Gondwana. @@ -3535,7 +3584,7 @@ Thanks to Bron Gondwana. 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. @@ -3549,7 +3598,7 @@ bug appeared in 0.5.0. 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. @@ -3562,7 +3611,7 @@ bug appeared in 0.5.0. 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. @@ -3658,7 +3707,7 @@ nginx nginx could not be built on 64-bit platforms; -bug appeared in 0.4.14. +the bug had appeared in 0.4.14. @@ -3692,7 +3741,7 @@ ngx_http_perl_module 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. @@ -3810,7 +3859,7 @@ and the deferred accept() were used. 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. @@ -3841,7 +3890,7 @@ Thanks to Thomas Moschny. the 50th subrequest in SSI response did not work; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. @@ -3911,7 +3960,7 @@ the ngx_http_perl_module supports the $r->allow_ranges method. 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. @@ -3958,7 +4007,7 @@ in the "map" directive. 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. @@ -3969,7 +4018,7 @@ nginx nginx could not be built on Debian amd64; -bug appeared in 0.4.9. +the bug had appeared in 0.4.9. @@ -4122,7 +4171,7 @@ the $r->headers_out("Content-Length", ...) method. 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. @@ -4138,7 +4187,7 @@ nginx nginx could not be built on Linux and Solaris; -bug appeared in 0.4.4. +the bug had appeared in 0.4.4. @@ -4260,7 +4309,7 @@ unix domain 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. @@ -4295,7 +4344,7 @@ of the Sun Studio PAUSE hardware capability bug. the O_NOATIME flag support on Linux was canceled; -bug appeared in 0.4.1. +the bug had appeared in 0.4.1. @@ -4400,7 +4449,7 @@ the "ssi" directive is available inside the "if" block. 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. @@ -4460,7 +4509,7 @@ had the captured escaped symbols from original URI. 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. @@ -4496,7 +4545,7 @@ the "dav_access" directive did not support three parameters. 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. @@ -4730,7 +4779,7 @@ was used and nginx switched to a next upstream. 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. @@ -4797,7 +4846,7 @@ nginx nginx could not be built on amd64 platform; -bug appeared in 0.3.53. +the bug had appeared in 0.3.53. @@ -4897,7 +4946,7 @@ to the 0.3.40 version state: the module now does not return the 405 error. 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. @@ -4910,7 +4959,7 @@ bug appeared in 0.3.37. 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. @@ -4937,7 +4986,7 @@ was not removed. the "<" symbols might disappeared some conditions in the SSI; -bug appeared in 0.3.50. +the bug had appeared in 0.3.50. @@ -5081,7 +5130,7 @@ X-Accel-Redirect, 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. @@ -5093,7 +5142,7 @@ bug appeared in 0.3.42. 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. @@ -5440,7 +5489,7 @@ SSI-commands, then the "unknown variable" message is not logged. 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. @@ -5451,7 +5500,7 @@ bug appeared in 0.2.0. the limit rate might not work on some condition; -bug appeared in 0.3.38. +the bug had appeared in 0.3.38. @@ -5687,7 +5736,7 @@ accept- 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. @@ -5761,7 +5810,7 @@ in the "post_action" directive. the debug logging on startup and reconfiguration time was removed; -bug appeared in 0.3.31. +the bug had appeared in 0.3.31. @@ -5820,7 +5869,7 @@ Thanks to Andrei Nigmatulin. 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. @@ -5875,7 +5924,7 @@ nginx 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. @@ -6108,7 +6157,7 @@ segmentation fault; 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. @@ -6163,7 +6212,7 @@ the first "proxy_redirect" directive was working inside one location. 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. @@ -6231,7 +6280,7 @@ the method $r->query_string of ngx_http_perl_module was canceled. 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. @@ -6392,7 +6441,7 @@ some ".domain.tld" names incorrectly processed by the ngx_http_map_module. segmentation fault was occurred if configuration file did not exist; -bug appeared in 0.3.12. +the bug had appeared in 0.3.12. @@ -6403,7 +6452,7 @@ bug appeared in 0.3.12. on 64-bit platforms segmentation fault may occurred on start; -bug appeared in 0.3.16. +the bug had appeared in 0.3.16. @@ -6437,7 +6486,7 @@ the "map" directive supports domain names in the ".domain.tld" form. the timeouts were not used in SSL handshake; -bug appeared in 0.2.4. +the bug had appeared in 0.2.4. @@ -6532,7 +6581,7 @@ nginx nginx did not close connection to IMAP/POP3 backend for the SSL connections; -bug appeared in 0.3.13.
+the bug had appeared in 0.3.13.
Thanks to Rob Mueller. @@ -6544,7 +6593,7 @@ segmentation fault segmentation fault may occurred in at SSL shutdown; -bug appeared in 0.3.13. +the bug had appeared in 0.3.13. @@ -6594,7 +6643,7 @@ quit and active "debug_points" directive. in the 304 response the body was transferred; -bug appeared in 0.3.13. +the bug had appeared in 0.3.13. @@ -6648,7 +6697,7 @@ to FastCGI-server via the unix domain socket. the "auth_basic" directive did not disable the authorization; -bug appeared in 0.3.11. +the bug had appeared in 0.3.11. @@ -6715,7 +6764,7 @@ the "proxy_buffering" directive. 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. @@ -6751,7 +6800,7 @@ the "Basic realm" text. 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. @@ -6787,7 +6836,7 @@ nginx 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. @@ -6923,7 +6972,7 @@ nginx 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. @@ -7057,7 +7106,7 @@ the worker processes did not flush the buffered logs on graceful exit. 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. @@ -7122,7 +7171,7 @@ nginx nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.3.2. +the bug had appeared in 0.3.2. @@ -7158,7 +7207,7 @@ nginx 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. @@ -7186,7 +7235,7 @@ segmentation fault; 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. @@ -7197,7 +7246,7 @@ accept mutex 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. @@ -7224,7 +7273,7 @@ nginx 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. @@ -7293,7 +7342,7 @@ after the -HUP signal nginx left an open socket in the CLOSED state. 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. @@ -7403,7 +7452,7 @@ directives. 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. @@ -7503,7 +7552,7 @@ new configuration, then the ngx_http_rewrite_module rules ran again. 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. @@ -7577,7 +7626,7 @@ in the "if" command. in proxying location without trailing slash; -bug appeared in 0.1.44. +the bug had appeared in 0.1.44. @@ -7588,7 +7637,7 @@ bug appeared in 0.1.44. 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. @@ -7604,7 +7653,7 @@ nginx nginx could not be built without the --with-debug option; -bug appeared in 0.2.2. +the bug had appeared in 0.2.2. @@ -7696,7 +7745,7 @@ the export versions of MSIE 5.x could not connect via HTTPS. 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. @@ -7956,7 +8005,7 @@ the FastCGI parameters with the empty values now are passed to a server. 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. @@ -7973,7 +8022,7 @@ segmentation fault 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. @@ -8002,7 +8051,7 @@ in the ngx_http_proxy_module. 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. @@ -8046,7 +8095,7 @@ did not logged in the error log. 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. @@ -8121,7 +8170,7 @@ the 401 response code redirecting. 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. @@ -8154,7 +8203,7 @@ the "include virtual" command. 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. @@ -8167,7 +8216,7 @@ bug appeared in 0.1.29. 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. @@ -8187,7 +8236,7 @@ the ngx_http_ssl_module did not support the certificate chain. 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. @@ -8283,7 +8332,7 @@ nginx 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. @@ -8466,7 +8515,7 @@ the "port_in_redirect" directive. 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. @@ -8502,7 +8551,7 @@ nginx nginx returned the 400 response on requests like "GET http://www.domain.com/uri HTTP/1.0"; -bug appeared in 0.1.28. +the bug had appeared in 0.1.28. @@ -8561,7 +8610,7 @@ nginx nginx could not be built with the --without-pcre parameter; -bug appeared in 0.1.29. +the bug had appeared in 0.1.29. @@ -8608,7 +8657,7 @@ the 500 error code was returned. 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. @@ -8681,7 +8730,7 @@ errors while using SSI and gzipping. 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. @@ -8717,7 +8766,7 @@ FastCGI 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. @@ -9000,7 +9049,7 @@ segmentation fault; 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. @@ -9391,7 +9440,7 @@ nginx nginx could not be built on platforms different from i386, amd64, sparc и ppc; -bug appeared in 0.1.22. +the bug had appeared in 0.1.22. @@ -9441,7 +9490,7 @@ statistics if the proxying or FastCGI server were used. the installation paths were incorrectly quoted on Linux and Solaris; -bug appeared in 0.1.21. +the bug had appeared in 0.1.21. @@ -9720,7 +9769,7 @@ then the segmentation fault occurred. 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. @@ -9806,7 +9855,7 @@ the rewrite directive supports the arguments rewriting. 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. @@ -9879,7 +9928,7 @@ the regular expressions in locations. the directive "proxy_preserve_host on" 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. @@ -9980,7 +10029,7 @@ and fastcgi_x_powered_by. the "[alert] zero size buf" error; -bug appeared in 0.1.3. +the bug had appeared in 0.1.3. @@ -10249,7 +10298,7 @@ the double slashes in "://" in the URI were converted to ":/". 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. @@ -10306,7 +10355,7 @@ sendfile64(). 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. @@ -10356,7 +10405,7 @@ the proxy_max_temp_file_size directive. 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. @@ -10550,7 +10599,7 @@ the portability improvements. 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. @@ -10573,7 +10622,7 @@ proxy module may get caught in an endless loop when sendfile is not used. 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.