Hi!
Unfortunately, I didn't find a very good solution for this, but, in nginx
1.4+ the issue with SSL backend keepalive was fixed - so if you have a list
of all your possible servers, your configuration file will look horrible,
but you can achieve this by having all the backend servers defined as
mamoos1 Wrote:
---
[snip...]
> I know that I can configure keep-alive with upstream - but that
> requires me to know upfront which servers will be used (which I don't,
> since I dynamically fetch content according to headers).
> Is there a way to
No it does not unless you don't configure a shared SSL session cache.
http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_session_cache
I'm assuming that the upstream servers are Nginx also.
If not adapt to the appropriate server session cache setup.
appa
On Tue, Apr 30, 2013 at 4:
A shame that no one has a solution for this...
It's a really big performance hit whenever backend servers are https and
nginx simply renegotiates SSL for each request.
Is there any plan to support this? Some sort of backend connection pooling
with SSL?
Posted at Nginx Forum:
http://forum.nginx.o
Hi,
I have an nginx configured as a reverse proxy using proxy_pass.
This is a dynamic reverse proxy, it fetches content for users in accordance
to the HOST header in the requests.
The problem I encountered is that the backends are normally SSL, and every
request that goes has to re-handshake (sinc
