hello,
the way to block ip's can also be used for PTR records, I think.
Also as wildcard.
On 21.05.2018 05:49, Sathish Kumar wrote:
> Hi All,
>
> I have a requirement to block certain countries coming to our website.
> I managed to achieved it using the ngx_http_geoip_module. I have a
> problem
> Rate limiting is a useful but crude tool that should only be one if four
or five different things you do to protect your backend:
>
> 1 browser caching
> 2 cDN
> 3 rate limiting
> 4 nginx caching reverse proxy
>
> What are your requests? Are they static content or proxied to a back end?
> Do
Hi All,
I have a requirement to block certain countries coming to our website. I
managed to achieved it using the ngx_http_geoip_module. I have a problem
now, if the request comes through Amazon API Gateway, how can I read the
X-forwarded-for header or block these request too.
nginx.conf
map $ge
5. Do you use keepslive?
Sent from my iPhone
> On May 20, 2018, at 2:45 PM, Peter Booth wrote:
>
> Rate limiting is a useful but crude tool that should only be one if four or
> five different things you do to protect your backend:
>
> 1 browser caching
> 2 cDN
> 3 rate limiting
> 4 nginx cac
Rate limiting is a useful but crude tool that should only be one if four or
five different things you do to protect your backend:
1 browser caching
2 cDN
3 rate limiting
4 nginx caching reverse proxy
What are your requests? Are they static content or proxied to a back end?
Do users login?
Is i
Hello.
I'm using nginx 1.14.0 on FreeBSD 11-STABLE. I'm trying to get caching
for internally generated content so I'm proxying nginx to nginx:
server {
listen unix:/home/someuser/.media.nginx.sock;
…
}
This perfectly works when starting nginx initially. However when
restarti
>>As I tried to explain in my previous message, "test runs for 60
>>seconds" can have two different meanings: 1) the load is generated
>>for 60 seconds and 2) from first request started to the last
>>request finished it takes 60 seconds.
>>Make sure you are using the correct meaning. Also, it m
