Welcome! Log In Create A New Profile

Advanced

Re: [PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

geniuss99
March 17, 2021 12:18PM
> From the design point of view, upstream{} blocks expect all
> connections to a peer to be equivalent.

I see your point.

One upstream block per static set of rules (connection-specific settings).

What I need is one upstream block per dynamic set of rules.
With current design this means creating as many upstream blocks as
there are sets of rules.

So if I have hundreds of such sets I will need to create hundreds of
identical upstream blocks with different names.
This is simple yet not flexible at all.

Sounds like we need new upstream module for such usecases, something
like "superupstream" :)
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

[PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

geniuss99 160 March 11, 2021 01:30PM

Re: [PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

Maxim Dounin 17 March 12, 2021 02:38PM

Re: [PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

geniuss99 17 March 16, 2021 10:44AM

Re: [PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

Maxim Dounin 15 March 16, 2021 07:26PM

Re: [PATCH] Keepalive: add new option "keepalive_ssl_respect_sni"

geniuss99 28 March 17, 2021 12:18PM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 71
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready