nginx-1.0.3-RELEASE

This commit is contained in:
Igor Sysoev 2011-05-25 14:50:50 +00:00
parent 5dc5945ccf
commit f56cdb3a3c

View File

@ -9,6 +9,75 @@
<title lang="en">nginx changelog</title>
<changes ver="1.0.3" date="25.05.2011">
<change type="feature">
<para lang="ru">
ÄÉÒÅËÔÉ×Á auth_basic_user_file ÐÏÄÄÅÒÖÉ×ÁÅÔ ÛÉÆÒÏ×ÁÎÉÅ ÐÁÒÏÌÑ
ÍÅÔÏÄÁÍÉ "$apr1", "{PLAIN}" É "{SSHA}".<br/>
óÐÁÓÉÂÏ íÁËÓÉÍÕ äÕÎÉÎÕ.
</para>
<para lang="en">
the "auth_basic_user_file" directive supports "$apr1", "{PLAIN}",
and "{SSHA}" password encryption methods.<br/>
Thanks to Maxim Dounin.
</para>
</change>
<change type="feature">
<para lang="ru">
ÄÉÒÅËÔÉ×Á geoip_org É ÐÅÒÅÍÅÎÎÁÑ $geoip_org.<br/>
óÐÁÓÉÂÏ áÌÅËÓÁÎÄÒÕ õÓËÏ×Õ, Arnaud Granal É äÅÎÉÓÕ ìÁÔÙÐÏ×Õ.
</para>
<para lang="en">
the "geoip_org" directive and $geoip_org variable.<br/>
Thanks to Alexander Uskov, Arnaud Granal, and Denis F. Latypoff.
</para>
</change>
<change type="feature">
<para lang="ru">
ÍÏÄÕÌÉ ngx_http_geo_module É ngx_http_geoip_module ÐÏÄÄÅÒÖÉ×ÁÀÔ
ÁÄÒÅÓÁ IPv4, ÏÔÏÂÒÁÖ£ÎÎÙÅ ÎÁ IPv6 ÁÄÒÅÓÁ.
</para>
<para lang="en">
ngx_http_geo_module and ngx_http_geoip_module support IPv4 addresses
mapped to IPv6 addresses.
</para>
</change>
<change type="bugfix">
<para lang="ru">
ÐÒÉ ÐÒÏ×ÅÒËÅ ÁÄÒÅÓÁ IPv4, ÏÔÏÂÒÁÖ£ÎÎÏÇÏ ÎÁ ÁÄÒÅÓ IPv6,
× ÒÁÂÏÞÅÍ ÐÒÏÃÅÓÓÅ ÐÒÏÉÓÈÏÄÉÌ segmentation fault,
ÅÓÌÉ ÄÉÒÅËÔÉ×Ù access ÉÌÉ deny ÂÙÌÉ ÏÐÒÅÄÅÌÅÎÙ ÔÏÌØËÏ ÄÌÑ ÁÄÒÅÓÏ× IPv6;
ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.22.
</para>
<para lang="en">
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.
</para>
</change>
<change type="bugfix">
<para lang="ru">
ÚÁËÜÛÉÒÏ×ÁÎÎÙÊ ÏÔ×ÅÔ ÍÏÇ ÂÙÔØ ÉÓÐÏÒÞÅÎ, ÅÓÌÉ ÚÎÁÞÅÎÉÑ ÄÉÒÅËÔÉ×
proxy/fastcgi/scgi/uwsgi_cache_bypass É proxy/fastcgi/scgi/ uwsgi_no_cache
ÂÙÌÉ ÒÁÚÎÙÍÉ;
ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.46.
</para>
<para lang="en">
a cached reponse 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.
</para>
</change>
</changes>
<changes ver="1.0.2" date="10.05.2011">
<change type="feature">