Hello Steve,
• Best answer is try and see if it meets your expectations; thanks
• While reading your snippet, my initial questions are — Why 2 servers?
Why not simplify?
• In your proposal: server1, listen to ?? TCP port(s) on public IPv4,
and IPv6 to proxy_pass to server2, then server2 listen
Hi,
We are using round-robin DNS to distribute requests to three servers
all running identically configured nginx. Connections then go upstream
to HAProxy and then to our Rails app.
About two weeks ago, users began to experience intermittent SSL
handshake errors. Users reported that these
It depends on the backend, really, but you cannot assume it will support
multiple sessions on the same connection. Maybe the backend needs the '1
connection = 1 request' relationship?
A backend supporting multiplexing won't have trouble with 1
request/connection, however, backend not supporting it
Hi
Le 31 janv. 2015 20:02, Richard Stanway r1ch+ng...@teamliquid.net a
écrit :
...
2015/01/13 12:22:59 [crit] 11871#0: *140260577 SSL_do_handshake()
failed (SSL: error:1408A0D7:SSL
routines:SSL3_GET_CLIENT_HELLO:required cipher missing) while SSL
handshaking, client: *.*.*.*, server:
Hi, how can tell nginx not to buffer client's requests? I need this
capability to upload files larger than the nginx's max buffering size. I got
an nginx unknown directive error when I tried the fastcgi_request_buffering
directive. Is the directive supported and I am missing a module in my nginx
It's a planned feature see (http://trac.nginx.org/nginx/roadmap)
But it has no ETA.
Kurt Cancemi
https://www.x64architecture.com
On Jan 31, 2015, at 11:25 PM, nginxuser100 nginx-fo...@nginx.us wrote:
Hi, how can tell nginx not to buffer client's requests? I need this
capability to upload
To add a bit more information.
Server1 is hosted, has both IPv4 and 6.
Server2 is on the end of an adsl line within a RFC1918 network where the
external port 80 points to another server which cannot be changed.
Another complication is that internet access from some client locations
is heavily