Hi Jens,
Thanks much for your explanation. I was sure about the first part and
was thinking more complexly on the second part I mean https upstream.
But your simple solution to this is awesome.
Kind Regards
Sajan
--
Posted via http://www.ruby-forum.com/.
_
Hello!
On Thu, Aug 22, 2013 at 01:03:01PM -0500, Sajan Parikh wrote:
> keepalives seem to be working, but the timeout limit I'm setting
> isn't honored it seems.. Someone let me know if I've done something
> wrong or am missing something.
[...]
> Yet, when I take a look at netstat -tc, I have
keepalives seem to be working, but the timeout limit I'm setting isn't
honored it seems.. Someone let me know if I've done something wrong or
am missing something.
I have nginx installed on Ubuntu from the stable repository at
nginx.org. Nothing has been added, nothing removed.
===
Thank you for the quick replay. I did it and they are looking at it.
I am adding link to the github issue about this one just for reference if
someone need it in future.
https://github.com/SpiderLabs/ModSecurity/issues/137
Regards,
Kiril
On Aug 22, 2013, at 6:16 PM, Alan Silva wrote:
> Hi Kiri
Hi Kiril,
I think the better place to make this question its on modsecurity users list,
because apparently its a problem in modsecurity module and don't in NGINX.
Regards,
Alan
On Aug 22, 2013, at 8:26 AM, Kiril Kalchev wrote:
> Hi,
>
> I have a problem with nginx and mod_security module.
Hi Sajan,
I see. nginx supports serving https content. Documentation is here:
http://nginx.org/en/docs/http/ngx_http_ssl_module.html
nginx also supports proxying to upstream servers that are using SSL/https:
http://stackoverflow.com/questions/15394904/nginx-load-balance-with-upstream-ssl
What y
Hi,
I have a problem with nginx and mod_security module. After reloading nginx
configuration (kill -HUP ) all files opened by mod_security
are opened once again without closing the old ones. That means at some point we
hit the limit of open file descriptors, in my real life scenario I leak over