# HG changeset patch # User Igor Sysoev # Date 1175510684 0 # Node ID d1ffcf84ea1244f659145c36ff28de6fcdf528b2 # Parent a4820184a61882f58814f98da10de90dbc0890e4 nginx-0.5.17-RELEASE diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml --- a/docs/xml/nginx/changes.xml +++ b/docs/xml/nginx/changes.xml @@ -9,6 +9,60 @@ nginx changelog + + + + +теперь nginx для метода TRACE всегда возвращает код 405. + + +now nginx always returns the 405 status for the TRACE method. + + + + + +теперь nginx поддерживает директиву include внутри блока types. + + +now nginx supports the "include" directive inside the "types" block. + + + + + +использование переменной $document_root в директиве root и alias +запрещено: оно вызывало рекурсивное переполнение стека. + + +the $document_root variable usage in the "root" and "alias" directives +is disabled: this caused recursive stack overflow. + + + + + +в использовании протокола HTTPS в директиве proxy_pass. + + +in the HTTPS protocol in the "proxy_pass" directive. + + + + + +в некоторых случаях некэшируемые переменные (такие, как $uri) +возвращали старое закэшированное значение. + + +in some cases non-cachable variables (such as $uri variable) +returned old cached value. + + + + + + @@ -3150,7 +3204,7 @@ bug appeared in 0.3.18. запросы с телом, записанным во временный файл. -if the HTTP protocol was used in the "proxy_pass" directive and +if the HTTPS protocol was used in the "proxy_pass" directive and the request body was in temporarily file then the request was not transferred. @@ -3384,7 +3438,7 @@ directive. запросы с телом. -if the HTTP protocol was used in the "proxy_pass" directive then +if the HTTPS protocol was used in the "proxy_pass" directive then the requests with the body was not transferred. @@ -3766,7 +3820,7 @@ bug appeared in 0.2.4. в использовании протокола HTTPS в директиве proxy_pass. -in the HTTP protocol in the "proxy_pass" directive. +in the HTTPS protocol in the "proxy_pass" directive. @@ -3776,7 +3830,7 @@ in the HTTP protocol in the "proxy_pass" использовался порт 80. -when the HTTP protocol was used in the "proxy_pass" directive the port 80 +when the HTTPS protocol was used in the "proxy_pass" directive the port 80 was used by default.