nginx-0.5.23-RELEASE
diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml
index e373f5c..c5d656b 100644
--- a/docs/xml/nginx/changes.xml
+++ b/docs/xml/nginx/changes.xml
@@ -9,6 +9,64 @@
<title lang="en">nginx changelog</title>
+<changes ver="0.5.23" date="04.06.2007">
+
+<change type="feature">
+<para lang="ru">
+ÍÏÄÕÌØ ngx_http_ssl_module ÐÏÄÄÅÒÖÉ×ÁÅÔ ÒÁÓÛÉÒÅÎÉÅ TLS Server Name Indication.
+</para>
+<para lang="en">
+the ngx_http_ssl_module supports Server Name Indication TLS extension.
+</para>
+</change>
+
+<change type="feature">
+<para lang="ru">
+ÄÉÒÅËÔÉ×Á fastcgi_catch_stderr.<br/>
+óÐÁÓÉÂÏ îÉËÏÌÁÀ çÒÅÞÕÈÕ, ÐÒÏÅËÔ OWOX.
+</para>
+<para lang="en">
+the "fastcgi_catch_stderr" directive.<br/>
+Thanks to Nick S. Grechukh, OWOX project.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+ÎÁ ìÉÎÕËÓÅ × ÏÓÎÏ×ÎÏÍ ÐÒÏÃÅÓÓÅ ÐÒÏÉÓÈÏÄÉÌ segmentation fault,
+ÅÓÌÉ Ä×Á ×ÉÒÔÕÁÌØÎÙÈ ÓÅÒ×ÅÒÁ ÄÏÌÖÎÙ bind()ÉÔÓÑ Ë ÐÅÒÅÓÅËÁÀÝÉÍÓÑ ÐÏÒÔÁÍ.
+</para>
+<para lang="en">
+a segmentation fault occurred in master process if
+two virtual servers should bind() to the overlapping ports.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+ÅÓÌÉ nginx ÂÙÌ ÓÏÂÒÁÎ Ó ÍÏÄÕÌÅÍ ngx_http_perl_module É perl
+ÐÏÄÄÅÒÖÉ×ÁÌ ÐÏÔÏËÉ, ÔÏ ×Ï ×ÒÅÍÑ ×ÔÏÒÏÊ ÐÅÒÅËÏÎÆÉÇÕÒÁÃÉÉ
+×ÙÄÁ×ÁÌÉÓØ ÏÛÉÂËÉ "panic: MUTEX_LOCK" É "perl_parse() failed".
+</para>
+<para lang="en">
+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.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+× ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÐÒÏÔÏËÏÌÁ HTTPS × ÄÉÒÅËÔÉ×Å proxy_pass.
+</para>
+<para lang="en">
+in the HTTPS protocol in the "proxy_pass" directive.
+</para>
+</change>
+
+</changes>
+
+
<changes ver="0.5.22" date="29.05.2007">
<change type="bugfix">
@@ -17,7 +75,7 @@
ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.5.21.
</para>
<para lang="en">
-the big request body might not be passed to backend;
+a big request body might not be passed to backend;
bug appeared in 0.5.21.
</para>
</change>
