details: https://hg.nginx.org/nginx/rev/f5a2af0e7079
branches:
changeset: 7693:f5a2af0e7079
user: Maxim Dounin
date: Thu Aug 06 05:02:57 2020 +0300
description:
Request body: optimized handling of small chunks.
If there is a previous buffer, copy small chunks into it instead of
details: https://hg.nginx.org/nginx/rev/0f7f1a509113
branches:
changeset: 7692:0f7f1a509113
user: Maxim Dounin
date: Thu Aug 06 05:02:55 2020 +0300
description:
Request body: allowed large reads on chunk boundaries.
If some additional data from a pipelined request happens to be
details: https://hg.nginx.org/nginx/rev/08ff2e10ae92
branches:
changeset: 7691:08ff2e10ae92
user: Maxim Dounin
date: Thu Aug 06 05:02:44 2020 +0300
description:
Request body: all read data are now sent to filters.
This is a prerequisite for the next change to allow large reads
on
details: https://hg.nginx.org/nginx/rev/8253424d1aff
branches:
changeset: 7690:8253424d1aff
user: Maxim Dounin
date: Thu Aug 06 05:02:22 2020 +0300
description:
Added size check to ngx_http_alloc_large_header_buffer().
This ensures that copying won't write more than the buffer size
Hello!
On Wed, Aug 05, 2020 at 06:07:43AM -0400, oradba25 wrote:
> Добрый день
>
> Долгое время работал сайт под управлением tomcat 7.0.75 с настройкой кеша
> под статику таким образом
>
> root/nginx/root/site;
> location ~ ^/tst/(css|custom|galleries|i|images)/ {
Hello!
On Wed, Aug 05, 2020 at 09:21:42PM +, Nica, George wrote:
> We are currently using "limit_req_zone $binary_remote_addr" for rate
> limiting. However, some of our users are connecting from more than one IP
> address, using clients running on computer grids.
> We wanted to do request
Hi, I am having some problems to load an app made in mvc, when I
access the url and I want to edit a table to make a change, the proxy
returns me to the root of the project, and it does not stay in
app/pais
I paste the url log, where it says it can't find resource 404
Hi,
We are currently using "limit_req_zone $binary_remote_addr" for rate limiting.
However, some of our users are connecting from more than one IP address, using
clients running on computer grids.
We wanted to do request rate limiting by authenticated user (in addition to the
existing one by
Добрый день
Долгое время работал сайт под управлением tomcat 7.0.75 с настройкой кеша
под статику таким образом
root/nginx/root/site;
location ~ ^/tst/(css|custom|galleries|i|images)/ {
expires 3h;
proxy_cache_valid 200 3h;
вот такая штука поможет ?
https://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_cache_lock
ср, 5 авг. 2020 г. в 11:39, Raice :
> Да, работает! Но получается, пока он файл не скачает, он будет просто
> проксировать на CDN все. Т.е. если одновременно клиенты начнут качать, то в
> итоге
Да, работает! Но получается, пока он файл не скачает, он будет просто
проксировать на CDN все. Т.е. если одновременно клиенты начнут качать, то в
итоге мы все равно получим N скачиваний с CDN, а клиенты все начинают качать
одновременно практически.
Posted at Nginx Forum:
Насколько понимаю, это должно работать в комплекте с proxy_store
https://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_store
Posted at Nginx Forum:
https://forum.nginx.org/read.php?21,288966,288972#msg-288972
___
nginx-ru mailing list
12 matches
Mail list logo