В 01:01 +0300 на 16.06.2013 (нд), Vasil Kolev написа:
> В 22:06 +0100 на 15.06.2013 (сб), Francis Daly написа:
>
> > The usual first step would be to see whether the problem persists when
> > you just use the distributed nginx, with no external modules or patches.
> >
> > But in this case, that's
On Sun, Jun 16, 2013 at 01:01:37AM +0300, Vasil Kolev wrote:
> В 22:06 +0100 на 15.06.2013 (сб), Francis Daly написа:
> > But in this case, that's probably unnecessary, since you already know
> > that without the "if" statements, no problems appear.
> > Perhaps using a "map" to set values to be u
В 22:06 +0100 на 15.06.2013 (сб), Francis Daly написа:
> The usual first step would be to see whether the problem persists when
> you just use the distributed nginx, with no external modules or patches.
>
> But in this case, that's probably unnecessary, since you already know
> that without the "
On Sat, Jun 15, 2013 at 04:32:04PM +0300, Vasil Kolev wrote:
Hi there,
> Removing the ifs in the config fixes the problem, but that doesn't help
> me :)
>
> This is a compiled nginx from source, on debian stable (wheezy), with a
> few small additions available at
> https://github.com/krokodileri
Hello,
I was trying to add rate limiting to our setup (mp4 file serving) and
got into some very strange issues.
First, with version 1.2.0, I was seeing the following:
2013/06/14 13:25:02 [emerg] 12470#0: *147816 malloc(18446744073709551608)
failed (12: Cannot allocate memory), client: 92.247.59
