Hello!
On Sat, Mar 16, 2013 at 09:32:27AM +1100, Robert Mueller wrote:
>
> > In case of https, in many (most) cases there are pending data -
> > due to various SSL packets send during connection close. This
> > means connection close detection with https doesn't work unless
> > you use kqueu
Hello!
On Sat, Mar 16, 2013 at 01:37:22AM -0700, Jay Oster wrote:
> Hi Maxim,
>
> Thanks for the suggestion! It looks like packet drop is the culprit here.
> The initial SYN packet doesn't receive a corresponding SYN-ACK from the
> upstream servers, so after a 1-second timeout (TCP Retransmissio
Hello!
On Fri, Mar 15, 2013 at 03:48:56PM -0400, beaufour wrote:
> I've been trying to get this setup working:
> client <- c0 -> nginx1 <- c1 -> nginx2 <- c2 -> service (http)
>
> where the c1 connection is kept alive between request from from the outside,
> but c0 and c2 are closed after each r
Thanks a lot, Jonathan and Francis!
It works great. I am able to significantly reduce the load. Here is my
final configuration:
*limit_req_zone $binary_remote_addr zone=ratezone:10m rate=3r/s;*
*server {*
* listen 80;*
* server_name www.example.com;*
*
*
* location / {*
*
OK - I now have Nginx running the 5 Thin app servers!
Thanks for the help!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237379,237441#msg-237441
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Without reading the whole file, what is the best approach to only check
if the beginning of the file contains a specific character?
Would something like this be the right approach?
b = ngx_pcalloc(r->pool, sizeof(ngx_buf_t));
b->file = ngx_pcalloc(r->pool, sizeof(ngx_file_t));
then se
Jay,
On Mar 16, 2013, at 12:37 PM, Jay Oster wrote:
> Hi Maxim,
>
> Thanks for the suggestion! It looks like packet drop is the culprit here. The
> initial SYN packet doesn't receive a corresponding SYN-ACK from the upstream
> servers, so after a 1-second timeout (TCP Retransmission TimeOut),
I agree with him too.
On 16 Mar 2013 08:46, "Nikolas Stevenson-Molnar"
wrote:
> I haven't tried it yet, but nginx-push-stream-module looks good:
> https://github.com/wandenberg/nginx-push-stream-module
>
> _Nik
>
> On 3/15/2013 4:24 PM, djczaski wrote:
> > What are the best options for websocket
Hi all!
There is a new subfilter module. It uses fast Wu-Manber algorithm for
multi-pattern search. Probably it would be interesting to someone:
https://github.com/dursegov/nginx-subfilter-module
It is possible to add regular expressions support if it is required, but as
a separate engine (i.e.
On Tue, Mar 12, 2013 at 05:39:27PM +0100, Jan-Philip Gehrcke wrote:
Hi there,
> I'm currently running a self-built nginx 1.3.14 on a debian system and
> use the attached (and also inlined) init.d script as /etc/init.d/nginx
> for managing the service. It's taken unmodified from debian wheezy.
On Sat, Mar 16, 2013 at 02:34:32AM -0700, Praveen Yarlagadda wrote:
Hi there,
> I installed nginx on an EC2 instance.
> Another weird thing is GET
> requests are starting with *"http://";. *I never saw it before. Is there any
> way I can filter requests or possibly throw 503?
These might be inn
On 16 March 2013 09:34, Praveen Yarlagadda wrote:
> Hi,
>
> I installed nginx on an EC2 instance. After few hours, I started getting
> repeated requests from a set of servers. I tried using limit_req with the
> following options:
>
> limit_req_zone $binary_remote_addr zone=ratezone:10m rate=3r/s;
Hi Maxim,
Thanks for the suggestion! It looks like packet drop is the culprit here.
The initial SYN packet doesn't receive a corresponding SYN-ACK from the
upstream servers, so after a 1-second timeout (TCP Retransmission TimeOut),
the packet is retransmitted. The question is still *why* this only
13 matches
Mail list logo