On 13 May 2015, at 05:17, Fabbbio wrote:
> I just install nginx 1.9 on my ubuntu 15.04 machine using precompiled
> package "apt-get install", nginx in working and now how can I add RTMP
> module?
You cannot add a module to a compiled nginx. To add a module you should
recompile it from source w
I just install nginx 1.9 on my ubuntu 15.04 machine using precompiled
package "apt-get install", nginx in working and now how can I add RTMP
module?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,258836,258836#msg-258836
___
nginx mailing lis
Hello!
On Tue, May 12, 2015 at 12:33:11PM -0400, jwroblewski wrote:
> Valentin V. Bartenev Wrote:
> ---
> > On Tuesday 12 May 2015 09:25:05 jwroblewski wrote:
> > > My use case is that upstreams are supposed to return within ~100ms,
> > > theref
On Tuesday 12 May 2015 12:33:11 jwroblewski wrote:
> Valentin V. Bartenev Wrote:
> ---
> > On Tuesday 12 May 2015 09:25:05 jwroblewski wrote:
> > > My use case is that upstreams are supposed to return within ~100ms,
> > > therefore using burst is
Valentin V. Bartenev Wrote:
---
> On Tuesday 12 May 2015 09:25:05 jwroblewski wrote:
> > My use case is that upstreams are supposed to return within ~100ms,
> > therefore using burst is not an option. I wanted to use limit_req to
> filter
> > out
On Tuesday 12 May 2015 16:46:29 B.R. wrote:
> I do not necessarily have a say on what is discussed here, but:
>
>1. I believe putting known limitations in the docs makes sense. Who
>defined the docs as sticking to the most common use cases? Technical docs
>are technical docs.
I'm agre
I do not necessarily have a say on what is discussed here, but:
1. I believe putting known limitations in the docs makes sense. Who
defined the docs as sticking to the most common use cases? Technical docs
are technical docs.
2. Using burst answers a specific need which has not been ex
On Tuesday 12 May 2015 09:25:05 jwroblewski wrote:
> My use case is that upstreams are supposed to return within ~100ms,
> therefore using burst is not an option. I wanted to use limit_req to filter
> out traffic which is exceeds my backend's processing capacity, but
> apparently it is not the righ
My use case is that upstreams are supposed to return within ~100ms,
therefore using burst is not an option. I wanted to use limit_req to filter
out traffic which is exceeds my backend's processing capacity, but
apparently it is not the right tool to use, if it only operates with
millisecond-precisi
On Monday 11 May 2015 10:59:46 jwroblewski wrote:
> Hi,
>
> I'm observing an inconsistent behavior of ngx_http_limit_req_module in nginx
> 1.7.12. The relevant excerpts from my config:
>
> http {
> ...
> # A fixed string used as a key, to make all requests fall into the same
> zone
> limi
Thanks Sergey,
I naively though every module being documented on the official website were
included.
There was/is no clear documentation about what is (not) included in the
official binary, helping people to decide whether it is feasible to switch
from custom builds to official ones.
Would it be
> On 11 May 2015, at 15:15, B.R. wrote:
>
> Hello,
>
> We are facing quite some trouble with the official nginx packages:
> their nginx -V does not show any sign of the GeoIP module.
Package never has geoip module, because it requires extra library (libgeoip).
Current policy is to include all
Hello,
We have 3 nginx web servers behind an nginx proxy and we were seeing "24:
Too many Open connections" error in nginx log of one server and found that
some of the users are getting 504 timed out error. We have observer that the
problem was only in one of the web-server. We restarted php_cgi &
hi
if you are using amazon you can try their DNS service Route53.
you can point the root domain to an ELB via ALIAS setting.
regards,
ron
On Mon, May 11, 2015 at 11:23 PM, braindeaf wrote:
> The SSL Checking service did indeed point out the error. I will admit to my
> own stupidity on this on
Has anyone else observed the same?
Is there any reason to that?
---
*B. R.*
On Mon, May 11, 2015 at 2:15 PM, B.R. wrote:
> Hello,
>
> We are facing quite some trouble with the official nginx packages:
> their nginx -V does not show any sign of the GeoIP module.
>
> Confirmed for:
> - Debian pack
15 matches
Mail list logo
