# HG changeset patch # User Maxim Dounin # Date 1328456060 0 # Node ID 5c97978d2717650cdac611ca6576767a943acbee # Parent 2840ff6b97bdc1b6cc76a0cd7ed0e6a1167eae9a Merge of r4379: duplicate words removed. 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 @@ -14431,7 +14431,7 @@ the bug had appeared in 0.3.3. если в директиве proxy_pass отсутствовал URI, то всегда использовался порт 80. -if the URI part is omitted in "proxy_pass" directive, the the 80 port was +if the URI part is omitted in "proxy_pass" directive, the 80 port was always used. @@ -15220,7 +15220,7 @@ the FastCGI parameters with the empty va the segmentation fault may occurred if there were errors while working with proxied or FastCGI server; -in the proxied mode the the bug had appeared in 0.1.29. +in the proxied mode the bug had appeared in 0.1.29. @@ -15237,7 +15237,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 the bug had appeared in 0.1.29. +in the proxied mode the bug had appeared in 0.1.29. @@ -15474,7 +15474,7 @@ Bugfixes in IMAP/POP3 proxy in interacti директива limit_rate поддерживается в режиме прокси и FastCGI. -the "limit_rate" directive is supported in in proxy and FastCGI mode. +the "limit_rate" directive is supported in proxy and FastCGI mode. @@ -15981,7 +15981,7 @@ FastCGI сервера была равна 500 байт, то nginx возвращал код ответа 500; 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 the bug had appeared in 0.1.29 only. +in proxy mode the bug had appeared in 0.1.29 only. @@ -16801,7 +16801,7 @@ nginx could not be built on NetBSD 2.0. во время чтения тела запроса клиента в SSL соединении мог произойти таймаут. -the timeout may occur while reading of the the client request body +the timeout may occur while reading of the client request body via SSL connections.