Is there any way I can impose a rate limit on a location or back-end
by HTTP method? Specifically I would like to limit the number of POST
requests that a single client IP can perform within a given timespan.
___
nginx mailing list
nginx@nginx.org
On Fri, Apr 4, 2014 at 12:33 PM, Knut Moe kmo...@gmail.com wrote:
Does anyone have updated instructions for 12.04?
sudo apt-get install nginx
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Mon, Feb 10, 2014 at 5:15 AM, Maxim Dounin mdou...@mdounin.ru wrote:
it is likely the cause, as the config includes the following lines:
proxy_cache_methods POST;
proxy_cache_key $request_method$request_uri$request_body;
Yikes I was not aware that the cache key gets stored into
On Thu, Feb 6, 2014 at 4:18 AM, Maxim Dounin mdou...@mdounin.ru wrote
Response headers should fit into proxy_buffer_size, see
http://nginx.org/r/proxy_buffer_size. If they don't, the error
is reported.
In which the size refers to the number of characters that appear up
till the blank line
On Sat, Jan 25, 2014 at 5:24 AM, Jonathan Kolb kolbyj...@gmail.com wrote:
You can chain two maps to get a logical and:
Thank you, this is precisely what I needed.
# note the lack of : after default in the maps, it's incorrect to have it
there like your original map did
Good catch, thanks.
On Fri, Jan 24, 2014 at 11:42 PM, wishmaster artem...@ukr.net wrote:
What is your proxy_cache_methods value?
I tried both
proxy_cache_methods OPTIONS;
as well as
proxy_cache_methods GET HEAD OPTIONS;
but both gave the error.
___
nginx
I use nginx to cache both GET and POST requests. I want to use
proxy_cache_bypass to allow users to bypass the cache, but ONLY for
GET requests. POST requests should always be cached. I tried this:
map $request_method $is_get {
default: ;
GET true;
}
proxy_cache_methods POST;
Is it possible to cache the OPTIONS method? This pages gives exactly
that example: http://www.packtpub.com/article/nginx-proxy
proxy_cache_methods OPTIONS;
However, when I try this, nginx writes in the error log:
[warn] 7243#0: invalid value OPTIONS in ...
On Fri, Jan 24, 2014 at 1:04 PM, B.R. reallfqq-ng...@yahoo.fr wrote:
Does the following work?
This looks like a fragile solution. You're basically simulating an
if, but I don't think we should assume that nginx will resolve all
maps in the defined order, as would be using if.
The nginx
On Mon, Nov 4, 2013 at 5:08 PM, Maxim Dounin mdou...@mdounin.ru wrote:
The proxy_redirect directive does string replacement, not URI
mapping. If you want it to replace /two/ with /one/, you can
configure it to do so. It's just not something it does by
default.
Exactly. I was trying to argue
with proxy_cache_bypass
Do I just need to add an additional line:
proxy_cache_bypass $request_body_file;
It is not clear to me how proxy_cache_bypass is different from proxy_no_cache.
On Fri, Sep 13, 2013 at 8:56 PM, Jeroen Ooms jeroeno...@gmail.com wrote:
Is it correct that when $content_length
@ Maxim Dounin
Thanks! This is very helpful. I have also set:
client_body_buffer_size 1m;
Could this setting have any side effects? I am not expecting too many
large POST request. From what I read, client_body_buffer_size is
actually the maximum amount of memory allocated. Does this mean that
Is it correct that when $content_length client_body_buffer_size,
then $request_body == ? If so this would be worth documenting at
request_body.
I am using:
proxy_cache_methods POST;
proxy_cache_key $request_method$request_uri$request_body;
Which works for small requests, but for large
13 matches
Mail list logo
