nginx changelog

From 1765f475445a054994611d2053cc181fb3504615 Mon Sep 17 00:00:00 2001 From: Igor Sysoev Date: Fri, 7 Jul 2006 16:33:19 +0000 Subject: nginx-0.3.53-RELEASE import *) Change: the "add_header" directive adds the string to 204, 301, and 302 responses. *) Feature: the "server" directive in the "upstream" context supports the "weight" parameter. *) Feature: the "server_name" directive supports the "*" wildcard. *) Feature: nginx supports the request body size more than 2G. *) Bugfix: if a client was successfully authorized using "satisfy_any on", then anyway the message "access forbidden by rule" was written in the log. *) Bugfix: the "PUT" method may erroneously not create a file and return the 409 code. *) Bugfix: if the IMAP/POP3 backend returned an error, then nginx continued proxying anyway. --- docs/html/50x.html | 8 +++-- docs/xml/nginx/changes.xml | 79 ++++++++++++++++++++++++++++++++++++++++++++-- 2 files changed, 82 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/html/50x.html b/docs/html/50x.html index b180ed281..836fb2d5a 100644 --- a/docs/html/50x.html +++ b/docs/html/50x.html @@ -6,9 +6,13 @@ body { font-family: Tahoma, Verdana, Arial, sans-serif; } -

+ + + + +
The page you are looking for is temporarily unavailable.
Please try again later. -
+
diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml index cb5cbb6d4..d894033e6 100644 --- a/docs/xml/nginx/changes.xml +++ b/docs/xml/nginx/changes.xml @@ -9,6 +9,79 @@ nginx changelog + + + + +директива add_header добавляет строки в ответы с кодом 204, 301 и 302. + + +the "add_header" directive adds the string to 204, 301, and 302 responses. + + + + + +директива server в блоке upstream поддерживает параметр weight. + + +the "server" directive if the "upstream" context supports +the "weight" parameter. + + + + + +директива server_name поддерживает маску "*". + + +the "server_name" directive supports the "*" wildcard. + + + + + +nginx поддерживает тело запроса больше 2G. + + +nginx supports the request body size more than 2G. + + + + + +если при использовании "satisfy_any on" клиент успешно проходил аутентификацию, +в лог всё равно записалоcь сообщение "access forbidden by rule". + + +if a client was successfully authorized using "satisfy_any on", then anyway +the "access forbidden by rule" message was written in the log. + + + + + +метод PUT мог ошибочно не создать файл и вернуть код 409. + + +the "PUT" method may erroneously not create a file and return the 409 code. + + + + + +если во время аутентификации IMAP/POP3 бэкенд возвращал ошибку, nginx +продолжал проксирование. + + +if the IMAP/POP3 backend returned an error, then nginx continued proxying +anyway. + + + + + + @@ -4510,8 +4583,8 @@ proxy_preserve_host сервера из директивы server_name. -if the request has no the "Host" header line, then the proxy_preserve_host -directive set this header line to the first server name of the server_name +if the request has no the "Host" header line, then the "proxy_preserve_host" +directive set this header line to the first server name of the "server_name" directive. @@ -5173,7 +5246,7 @@ the server_names_hash and server_names_hash_threshold directives. имена *.domain.tld в директиве server_name не работали. -the *.domain.tld names in the server_name directive did not work. +the *.domain.tld names in the "server_name" directive did not work. -- cgit