From 85ef94ba857237882c7e68dea87a1dbc68a38fe7 Mon Sep 17 00:00:00 2001 From: Igor Sysoev Date: Thu, 23 Jun 2005 13:41:06 +0000 Subject: nginx-0.1.37-RELEASE import *) Change: now the "\n" is added to the end of the "nginx.pid" file. *) Bugfix: the responses may be transferred not completely, if many parts or the big parts were included by SSI. *) Bugfix: if all backends had returned the 404 reponse and the "http_404" parameter of the "proxy_next_upstream" or "fastcgi_next_upstream" directives was used, then nginx started to request all backends again. --- docs/xml/nginx/changes.xml | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) (limited to 'docs/xml') diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml index 16ca64b22..362db2391 100644 --- a/docs/xml/nginx/changes.xml +++ b/docs/xml/nginx/changes.xml @@ -9,6 +9,44 @@ nginx changelog + + + + +в конце файла nginx.pid теперь добавляется "\n". + + +now the "\n" is added to the end of the "nginx.pid" file. + + + + + +при включении большого количества вставок или нескольких больших вставок +с помощью SSI ответ мог передаваться не полностью. + + +the responses may be transferred not completely, +if many parts or the big parts were included by SSI. + + + + + +если все бэкенды возвращали ответ 404, то при использовании параметра http_404 +в директивах proxy_next_upstream или fastcgi_next_upstream, nginx +начинал запрашивать все бэкенды снова. + + +if all backends had returned the 404 reponse and the "http_404" parameter of +the "proxy_next_upstream" or "fastcgi_next_upstream" directives was used, +then nginx started to request all backends again. + + + + + + -- cgit