Hi,
I'm doing this: limit_req_status 429;
The module HttpLimitReqModule delivers "nginx/1.4.3" (at least with version
1.4.3) as a message for the HTTP status code 429. That is too generic and
not useful at all. Why doesn't it deliver a "Too Many Requests" message
instead of that? It is absurd, u
Hi,
tonight I force-restarted nginx and everything seems to be fixed.
Checking the sockets shortly after restart returned 48 sockets for the
master process and 36 sockets for worker processes.
Now, 14 hours later sockets raise again - there are now 1128 sockets for
the master and 1116 for w
Oh, ok. Then it is similar to REGEX in Java.
Well, then I think I have a nice and elegant solution, Thanks!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,244015,244149#msg-244149
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.o
On Fri, Oct 25, 2013 at 07:07:20PM -0400, Brian08275660 wrote:
Hi there,
> ~*(.*)X
>
> I think that the first two characters mean "match anycase", then the "(.*)"
> would mean "any quantity of characters" and the "X" would mean that specific
> letter.
>
> Am I right?
Yes.
But unless you're go
On Fri, Oct 25, 2013 at 02:44:57PM -0700, Paul N. Pace wrote:
> On Wed, Oct 23, 2013 at 11:41 AM, Francis Daly wrote:
> > On Wed, Oct 23, 2013 at 11:32:33AM -0700, Paul N. Pace wrote:
Hi there,
> Hi Francis, and again thanks for your help in this matter. I would
> have responded sooner but the d
Hi List,
i have a strange performance-issue on a server that serves
static-files only (http + https), if files are bigger than 5k:
- rps drops from 6500 rps (empty file) to 13 rps when requesting a file >
5k
- perftest with location /perftest/ is at 8000 rps (https) / 15000 rps
(http)
- perftest
