Welcome! Log In Create A New Profile

Advanced

Re: [warn] a client request body is buffered to a temporary file

Илья Шипицин
July 12, 2022 03:28PM
ср, 13 июл. 2022 г. в 00:16, Gena Makhomed <gmm@csdoc.com>:

> On 12.07.2022 20:12, Илья Шипицин wrote:
>
> >> и еще примерно 20% - это "предупреждения" о том, что
> >> a client request body is buffered to a temporary file
>
> > это же можно выключить через proxy_request_buffering ?
>
> Да, в моем случае - это вполне подходит, спасибо.
>
> proxy_http_version 1.1;
> proxy_request_buffering off;
>
> Потому что у меня у каждого nginx frontend
> есть всего один nginx backend для каждого сайта:
> nginx frontend <=> nginx backend <=> php-fpm
>
> Самое главное - не забыть включить директиву proxy_http_version 1.1;
> на nginx frontend, иначе будут проблемы из-за использования HTTP/1.0
>
>
> https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering
>
> When HTTP/1.1 chunked transfer encoding is used to send the original
> request body, the request body will be buffered regardless of the
> directive value unless HTTP/1.1 is enabled for proxying.
>

HTTP/1.1 обычно включаю, но до этого места в документации про chunked не
дочитал ))


>
> >> Еще - было бы очень хорошо, чтобы nginx умел писать логи на диск
> >> не до тех пор, пока там останется 0 байт свободного места, а хотя
> >> бы оставлял 1 гигабайт для файлов в /var/cache/nginx/client_temp
>
> > буферизация на диск имеет кучу побочных эффектов.
> > можно через Модуль ngx_http_proxy_module (nginx.org)
> > <
> https://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_max_temp_file_size
> >
> > выключить дисковую часть (оставив буферизацию в памяти)
>
> Директива proxy_max_temp_file_size 0; на nginx frontend у меня прописана
> Но она влияет только на буферизацию проксируемых от backend`ов ответов.
>
> Полностью отключить использование диска nginx frontend
> для проксирования и запросов и ответов можно
> с помощью такого набора директив:
>
> proxy_http_version 1.1;
> proxy_request_buffering off;
> proxy_max_temp_file_size 0;
>

не совсем верно. если не трогать proxy_buffering, то ответы буферизуются (в
памяти, но не на диске)


>
> Однако это имеет смысл только в том случае, если nginx frontend
> проксирует запросы на nginx backend, на котором включена буферизация


если у бекенда форк-модель, и дорогое подключение, которое желательно
максимально быстро освободить, даже ценой буферизации на диск, то да.
для многих современных бекендов, включач php-fpm, поддержание 10к
одновременных подключений не является проблемой, кажется, что буферизация
на диск скорее избыточна, и по факту не решает никаких проблем, но может их
создать

>
> запросов и ответов на диск. Если в качестве backend`а используется
> httpd apache - использование диска для буферизации
> наверное лучше будет не выключать.
>

верно


>
> --
> Best regards,
> Gena
> _______________________________________________
> nginx-ru mailing list -- nginx-ru@nginx.org
> To unsubscribe send an email to nginx-ru-leave@nginx.org
>
_______________________________________________
nginx-ru mailing list -- nginx-ru@nginx.org
To unsubscribe send an email to nginx-ru-leave@nginx.org
Subject Author Posted

400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 05, 2022 05:49AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Илья Шипицин July 05, 2022 06:34AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 05, 2022 06:57AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Илья Шипицин July 05, 2022 07:16AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 05, 2022 02:12PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 05, 2022 08:56AM

certbot

Gena Makhomed July 05, 2022 03:10PM

Re: certbot

Maxim Dounin July 05, 2022 05:54PM

Re: certbot

Gena Makhomed July 06, 2022 02:02AM

Re: certbot

Maxim Dounin July 06, 2022 03:02PM

Re: certbot

Gena Makhomed July 06, 2022 04:40PM

Re: certbot

Maxim Dounin July 06, 2022 06:20PM

Re: certbot

Evgeniy Berdnikov July 07, 2022 05:20AM

Re: certbot

Илья Шипицин July 07, 2022 05:42AM

Re: certbot

Evgeniy Berdnikov July 07, 2022 06:16AM

Re: certbot

Илья Шипицин July 07, 2022 06:40AM

Re: certbot

Dmitry Morozovsky July 20, 2022 01:00PM

Re: certbot

Maxim Dounin July 20, 2022 04:02PM

Re: certbot

Илья Шипицин July 21, 2022 06:44AM

Re: certbot

Илья Шипицин July 21, 2022 06:48AM

OCSP Must Staple

Gena Makhomed July 21, 2022 07:06AM

Re: OCSP Must Staple

Илья Шипицин July 21, 2022 07:14AM

Re: OCSP Must Staple

Maxim Dounin July 21, 2022 09:30PM

Re: certbot

raven_kg@megaline.kg July 06, 2022 02:10AM

Re: certbot

milov July 06, 2022 04:49AM

Re: certbot

Илья Шипицин July 06, 2022 07:46AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 05, 2022 03:40PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 05, 2022 07:06PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 05, 2022 07:20PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 05, 2022 09:54PM

long deprecated directives

Gena Makhomed July 06, 2022 01:18AM

Re: long deprecated directives

Maxim Konovalov July 06, 2022 02:30AM

Re: long deprecated directives

Maxim Dounin July 06, 2022 03:16PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 06, 2022 04:44AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 06, 2022 03:22PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 07, 2022 04:34AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Антон Горлов via nginx-ru July 07, 2022 04:46AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 07, 2022 04:57AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 07, 2022 03:16PM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

milov July 09, 2022 04:46AM

Re: 400 Bad Request The plain HTTP request was sent to HTTPS port

Maxim Dounin July 10, 2022 04:42AM

SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking

Gena Makhomed July 11, 2022 02:08PM

Re: SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking

Maxim Dounin July 11, 2022 09:26PM

Re: SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking

Sergey Kandaurov July 12, 2022 07:54AM

Re: SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking

Maxim Dounin July 12, 2022 10:00AM

[error] access forbidden by rule

Gena Makhomed July 12, 2022 09:48AM

Re: [error] access forbidden by rule

Илья Шипицин July 12, 2022 10:42AM

Re: [error] access forbidden by rule

Maxim Dounin July 12, 2022 10:52AM

Re: [error] access forbidden by rule

Gena Makhomed July 12, 2022 12:56PM

Re: [error] access forbidden by rule

Илья Шипицин July 12, 2022 01:14PM

[warn] a client request body is buffered to a temporary file

Gena Makhomed July 12, 2022 03:16PM

Re: [warn] a client request body is buffered to a temporary file

Илья Шипицин July 12, 2022 03:28PM

Re: [warn] a client request body is buffered to a temporary file

Gena Makhomed July 12, 2022 05:02PM

Re: [warn] a client request body is buffered to a temporary file

Илья Шипицин July 12, 2022 11:44PM

Re: [error] access forbidden by rule

Илья Шипицин July 12, 2022 01:18PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 86
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready