Whitelisting Req/Conn Limiting

B.R. reallfqq-nginx at yahoo.fr
Sun Jun 1 12:09:34 UTC 2014


I am glad my explanations were clear enough, though I doubt I said more
than the docs which, again, seem pretty clear to me.
You could make suggestions on how to improve the docs by quoting what you
think would gain to be rephrased better.

Based on my previous advice, you already know that using 'if' is avoidable
and recommended.
What do you think you could change to match your new needs?
At which level does the check should be done?
How to use variables to make only targeted environments affected by you
contional statement?

You could search archives of the ML on the forum you are using since map
configuration are a recurring question, and your use case has been
addressed multiple times in the past.

To increase your chances to gain help, please provide:
- details on the process you followed
- relevant bits of the configuration you achieved which bother you
- intel about searches/thinking you made
- precise questions/wondering you have
---
*B. R.*


On Sun, Jun 1, 2014 at 11:02 AM, SupaIrish <nginx-forum at nginx.us> wrote:

> Thanks for the reply
>
> 1) Your explanation clarified my misunderstanding, much appreciated.
>
> 2) Your suggestion would make a lot of sense.  But after reading your
> response, I realized I wrote the check wrong in my example.  I'm trying to
> whitelist an inbound request from a specific server, not one that Nginx is
> serving.  Instead of $hostname I should be using $remote_addr and the IP of
> the remote server I'm attempting to whitelist from the throttling.  i.e.
>
> if ( $remote_addr = XX.XXX.XXX.XXX ) {
>   set $whitelist 1;
> }
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,250510,250530#msg-250530
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140601/532be8e0/attachment.html>


More information about the nginx mailing list