mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-18 18:19:39 -05:00
83b3e2876e
ssl/set_ssl_cert.vtc was renamed to ssl/set_ssl_cert.vtci
to produce a common part runnable both for QUIC and TCP listeners.
Then set_ssl_cert.vtc files were created both under ssl and quic directories
to call this .vtci file with correct VTC_SOCK_TYPE environment values
("quic" for QUIC listeners and "stream" for TCP listeners);
28 lines
1.3 KiB
Text
28 lines
1.3 KiB
Text
#REGTEST_TYPE=devel
|
|
|
|
# This reg-test uses the "set ssl cert" command to update a certificate over the CLI.
|
|
# It requires socat to upload the certificate
|
|
#
|
|
# This check has two separate parts.
|
|
# In the first part, there are 3 requests, the first one will use "www.test1.com" as SNI,
|
|
# the second one with the same but that must fail and the third one will use
|
|
# "localhost". Since vtest can't do SSL, we use haproxy as an SSL client with 2
|
|
# chained listen section.
|
|
#
|
|
# In the second part, we check the update of a default certificate in a crt-list.
|
|
# This corresponds to a bug raised in https://github.com/haproxy/haproxy/issues/1143.
|
|
# A certificate is used as default certificate as well as regular one, and during the update
|
|
# the default certificate would not be properly updated if the default instance did not have
|
|
# any SNI. The test consists in checking that the used certificate is the right one after
|
|
# updating it via a "set ssl cert" call.
|
|
#
|
|
# If this test does not work anymore:
|
|
# - Check that you have socat
|
|
|
|
varnishtest "Test the 'set ssl cert' feature of the CLI"
|
|
# QUIC backend are not supported with USE_QUIC_OPENSSL_COMPAT
|
|
feature cmd "$HAPROXY_PROGRAM -cc 'feature(QUIC) && !feature(QUIC_OPENSSL_COMPAT) && !feature(OPENSSL_WOLFSSL)'"
|
|
feature cmd "command -v socat"
|
|
|
|
setenv VTC_SOCK_TYPE quic
|
|
include ${testdir}/../ssl/set_ssl_cert.vtci
|