the main problem is here
when i change max_ranges to 0
for example i want to disable range request header ! , or multipart download
, or resemble download !
nginx ignore that
i dont know why .
i need limit it to 2 connection.
but no value effective on this directive :(
nginx ignore it ...
Pos
Isn't multipart the means to speed up downloading with multiple streams? So
wouldn't rate limiting solve the problem?
Original Message
From: li...@lazygranch.com
Sent: October 18, 2017 3:15 PM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject: Re: max_ranges not working
This needs furt
This needs further explaining. If you rate limit, a multiple connection
download manager won't download any faster.
Original Message
From: li...@lazygranch.com
Sent: October 18, 2017 3:13 PM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject: Re: max_ranges not working
I know max connec
I know max connections will solve this, but the drawback is you could have some
large user behind a NAT, which would lock out users. I used a multiple
connection download manager to verify this.
This ranges feature sounds great. I look forward to you getting it to work. ;-)
Original Messag
hi ,
we are under heavy request storm .
i seted
max_ranges 0;
to stop multirange requests "multipart download"
but it not working i see 10 concurrent download follow in each file .
i need to limit this value to 2 maximum range request per file.
i usig aio threads.
any way any body help me to fi
Have you tried using 307 or 308 redirect codes?
It works for any request which contains a body like POST\PUT\OTHERS.
Eliezer
http://ngtech.co.il/lmgtfy/
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of
Hello all,
We are seeing this error in NGINX logs, when the response is being read back
from the upstream servers.
SSL_read() failed (SSL: error:14094438:SSL routines:ssl3_read_bytes:tlsv1
alert internal error:SSL alert number 80) while reading response header from
upstream"
Could you please sug
rather, $request_uri
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276946,276949#msg-276949
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Also - our standardization is not the greatest, so I actually want to
rewrite the entire URI, which is why I have ^/(.*) as the regex. However I
don't think the $1 in the replacement string will still apply to the
original URI. Would this work?
location ~* /v1/device/(.*)/ {
rewrite $uri /api/v1.
Hi,
In order to support HTTP and HTTPS on the same port we had to enable SSL
for that listen port in the nginx config and remap the 497 nginx error code
to a permanent redirect. To be transparent to the client making the request
(written in go), we used "error_page 497 301 =200 $request_uri;".
Th
I'm trying to setup rewrites so I can automate this more efficiently. Some
of my locations require a rewrite and some do not. I currently have it
hardcoded into the proxy_pass:
location ~* /v1/device/(.*)/ {
proxy_pass http://api.domain.com/api/v1.0/download/$1;
}
Would this accomplish the
Hi Philip,
Yes. The link which you referred to, definitely tries to address quite a
similar problem as what I had described earlier.
I need to get more familiar with Lua and its usage with NGINX.
Thanks for your reply.
Regards,
Rajesh
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2
You can't say that. Which fpm model are you using? dynamic, ondemand? Makes a
huge difference.
If you have a memory leak, ensure your workers are killed on a regular basis.
Don't want you near my servers for sure!
Steve
October 18, 2017 1:17 PM, "Peter Booth" wrote:
Agree,
I work as perform
13 matches
Mail list logo
