Is your feature request to resolve a problem or provide enhanced functionality? Please describe.
Enhanced functionality; resolution of edge cases
Describe the solution you would like
Currently as of #804, enable_sni can be specified.
This allows for MOST cases with e.g. HTTPS virtual hosting (e.g. balancing web servers/proxies) to work correctly.
However, there is no way to specify a different SNI name than that of the host in the url { virtualhost } block (or the virtual server etc.).
In some (admittedly rare, but I wouldn't be opening this if I didn't run into it), it is desirable to use a different SNI name than that of the virtualhost.
Describe alternatives you have considered
N/A
Would the feature request be of benefit only to you, or is it more generally applicable?
In more complex setups (e.g. TLS stream proxies, etc.), it allows for more advanced routing (OSI layers 4/5 vs. layer 7).
Keepalived version
2.3.4
Additional context
N/A
Is your feature request to resolve a problem or provide enhanced functionality? Please describe.
Enhanced functionality; resolution of edge cases
Describe the solution you would like
Currently as of #804,
enable_snican be specified.This allows for MOST cases with e.g. HTTPS virtual hosting (e.g. balancing web servers/proxies) to work correctly.
However, there is no way to specify a different SNI name than that of the host in the
url { virtualhost }block (or the virtual server etc.).In some (admittedly rare, but I wouldn't be opening this if I didn't run into it), it is desirable to use a different SNI name than that of the
virtualhost.Describe alternatives you have considered
N/A
Would the feature request be of benefit only to you, or is it more generally applicable?
In more complex setups (e.g. TLS stream proxies, etc.), it allows for more advanced routing (OSI layers 4/5 vs. layer 7).
Keepalived version
2.3.4
Additional context
N/A