IntenseWebs/nginx
3
0
Fork 0
mirror of https://github.com/nginx/nginx.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

Words duplications removed.

Browse Source
This commit is contained in:
Maxim Konovalov
2011-12-24 06:31:57 +00:00
parent aa4492612b
commit 4c2f2d52bd
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/xml/nginx/changes.xml
View File

@@ -14812,7 +14812,7 @@ the bug had appeared in 0.3.3.
если в директиве proxy_pass отсутствовал URI, то всегда использовался порт 80. если в директиве proxy_pass отсутствовал URI, то всегда использовался порт 80.
</para> </para>
<para lang="en"> <para lang="en">
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. always used.
</para> </para>
</change> </change>
@@ -15601,7 +15601,7 @@ the FastCGI parameters with the empty values now are passed to a server.
<para lang="en"> <para lang="en">
the segmentation fault may occurred if there were errors while the segmentation fault may occurred if there were errors while
working with proxied or FastCGI server; 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.
</para> </para>
</change> </change>
@@ -15618,7 +15618,7 @@ segmentation fault или рабочий процесс мог зациклит
the segmentation fault occurred or the worker process may got caught 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" in an endless loop if the proxied or FastCGI server sent the "Cache-Control"
header line and the "expires" directive was used; 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.
</para> </para>
</change> </change>
@@ -15855,7 +15855,7 @@ Bugfixes in IMAP/POP3 proxy in interaction with a backend at the login state.
директива limit_rate поддерживается в режиме прокси и FastCGI. директива limit_rate поддерживается в режиме прокси и FastCGI.
</para> </para>
<para lang="en"> <para lang="en">
the "limit_rate" directive is supported in in proxy and FastCGI mode. the "limit_rate" directive is supported in proxy and FastCGI mode.
</para> </para>
</change> </change>
@@ -16362,7 +16362,7 @@ FastCGI сервера была равна 500 байт, то nginx возвра
<para lang="en"> <para lang="en">
if the length of the response part received at once from proxied 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; 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.
</para> </para>
</change> </change>
@@ -17182,7 +17182,7 @@ nginx could not be built on NetBSD 2.0.
во время чтения тела запроса клиента в SSL соединении мог произойти таймаут. во время чтения тела запроса клиента в SSL соединении мог произойти таймаут.
</para> </para>
<para lang="en"> <para lang="en">
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. via SSL connections.
</para> </para>
</change> </change>