--- Original message ---
From: "Maxim Dounin"
Date: 3 September 2013, 17:58:00
> Hello!
>
> On Tue, Sep 03, 2013 at 10:39:49AM -0400, bkosborne wrote:
>
> > I'm working on a configuration for an nginx proxy that splits requests
> > between two upstream servers. The main reason I'm using a
Hello
I am using Nginx with Circus. Circus is used with chaussette
Very rarely I am seeing 504 error
Nginx error log says
upstream timed out (110: Connection timed out) while reading response header
from upstream, client: A.B.C.D, server: servername.com, request: "GET /
HTTP/1.1", upstream: "
I'm working on a configuration for an nginx proxy that splits requests
between two upstream servers. The main reason I'm using a proxy is for SSL
termination and for redundancy between the two upstream servers. Each
upstream server is just a simple nginx server with identical media files
stored on
Hello!
On Tue, Sep 03, 2013 at 10:39:49AM -0400, bkosborne wrote:
> I'm working on a configuration for an nginx proxy that splits requests
> between two upstream servers. The main reason I'm using a proxy is for SSL
> termination and for redundancy between the two upstream servers. Each
> upstrea
One thing I thought of is that proxy_buffering is ideal if you have slow
clients - where downloading the media files could take a long time. In this
case, the goal would be to free up upstream workers. However, since my
upstream is NOT an application server, and just nginx, is that really
necessary
Hello!
On Tue, Sep 03, 2013 at 02:19:32PM +0100, Richard Kearsley wrote:
> Ah, let me guess - is the keepalive number "per worker"?
Sure, and it's what documentation explicitly states, see
http://nginx.org/r/keepalive:
: The connections parameter sets the maximum number of idle
: keepalive con
Ah, let me guess - is the keepalive number "per worker"?
On 03/09/13 13:42, Richard Kearsley wrote:
Hi
I seem to have an issue where the upstream keepalives aren't being
re-used
It shouldn't ever need more than 500 connections to the upstream, but
it keeps making more? and doesn't stick to t
I'm using ngnix as proxy server. There is a situation when backend server is
down and I know about it. Thus I'm adding 'Check-Cache' header to request
and what I want to do is get the file when it is in cache, and when it is
not just return error page. I don't want to pass the request to the
backen
Hi
I seem to have an issue where the upstream keepalives aren't being re-used
proxy_http_version 1.1;
upstream dev1 {
server 10.0.0.11 max_fails=0;
keepalive 1024;
}
location /
{
proxy_pass http://dev1;
proxy_set_header Connection "";
}
On a separate server I run 'ab -n 500 -c
Hello!
On Tue, Sep 03, 2013 at 01:22:36AM -0400, rmombassa wrote:
> I am setting up nginx as POP3 mail proxy to two 3rd party mail servers.
> Different domains, one of them uses SSL.
>
> Since I do not have that 3rd party's SSL certificate I use my own company
> certificate in nginx. That cert i
Hello folks!
I am glad to announce that the new development version of
ngx_openresty, 1.4.2.3, is now released:
http://openresty.org/#Download
Special thanks go to all the contributors for making this happen!
Below is the complete change log for this release, as compared to the
last (devel)
11 matches
Mail list logo