Rolled into production and after tens of thousands of page requests only 3
were smacked down and all were bogus security scanners or "bad dudes"
MISSION ACCOMPLISHED! Thanks a ton Maxim!
On Wed, Nov 13, 2013 at 10:20 AM, Justin Deltener
wrote:
> I'll give that a try. I real
I'll give that a try. I really appreciate your help Maxim!
On Wed, Nov 13, 2013 at 10:01 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Nov 13, 2013 at 09:09:55AM -0600, Justin Deltener wrote:
>
> > Aha, that is the lightbulb moment.
> >
> > So if we're ta
et the default rate to 1/m and set the burst to whatever
you like..
Does that make sense?
On Wed, Nov 13, 2013 at 7:40 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Nov 13, 2013 at 07:17:36AM -0600, Justin Deltener wrote:
>
> [...]
>
> > current requests..which is what i
tive under a single proxy location directive.
5) Thanks for the link, but I have read that document a hundred times and
there is still a ton that it doesn't cover.
I appreciate your response Maxim!
On Wed, Nov 13, 2013 at 5:27 AM, Maxim Dounin wrote:
> Hello!
>
> On Tue, No
For the life of me I can't seem to get my configuration correct to limit
requests. I'm running nginx 1.5.1 and have it serving up static content and
pushing all non-existent requests to the apache2 proxy backend for serving
up. I don't want to limit any requests to static content but do want to
lim
