haproxy/reg-tests
Remi Tricot-Le Breton 8218aed90e BUG/MINOR: ssl: Fix update of default certificate
The default SSL_CTX used by a specific frontend is the one of the first
ckch instance created for this frontend. If this instance has SNIs, then
the SSL context is linked to the instance through the list of SNIs
contained in it. If the instance does not have any SNIs though, then the
SSL_CTX is only referenced by the bind_conf structure and the instance
itself has no link to it.
When trying to update a certificate used by the default instance through
a cli command, a new version of the default instance was rebuilt but the
default SSL context referenced in the bind_conf structure would not be
changed, resulting in a buggy behavior in which depending on the SNI
used by the client, he could either use the new version of the updated
certificate or the original one.

This patch adds a reference to the default SSL context in the default
ckch instances so that it can be hot swapped during a certificate
update.

This should fix GitHub issue #1143.

It can be backported as far as 2.2.
2021-03-26 13:06:29 +01:00
..
balance REGTEST: fix host part in balance-uri-path-only.vtc 2020-09-29 10:52:27 +02:00
cache REGTESTS: Fix required versions for several scripts 2021-01-28 16:37:14 +01:00
checks MEDIUM: server: support {check,agent}_addr, agent_port in server state 2021-02-12 16:04:52 +01:00
compression CLEANUP: assorted typo fixes in the code and comments 2021-01-06 16:26:50 +01:00
connection REGTESTS: revert workaround for a crash with recent libressl on http-reuse sni 2021-03-20 09:32:57 +01:00
contrib REGTESTS: contrib/prometheus-exporter: test well known labels 2021-02-19 18:03:59 +01:00
converter BUG/MINOR: sample: Rename SenderComID/TargetComID to SenderCompID/TargetCompID 2021-03-10 10:44:20 +01:00
filters BUG/MEDIUM: filters/htx: Fix data forwarding when payload length is unknown 2021-01-26 09:53:52 +01:00
http-capture REGTEST: rename the reg test files. 2019-04-23 15:37:03 +02:00
http-cookies MEDIUM: proxy: remove start_proxies() 2020-10-09 11:27:30 +02:00
http-errorfiles BUG/MINOR: http-rules: Fix ACLs parsing for http deny rules 2020-06-30 09:32:03 +02:00
http-messaging REGTESTS: Add a script to test payload skipping for bodyless HTTP responses 2021-02-10 16:25:42 +01:00
http-rules REGTESTS: Add script to test except param for fowardedfor/originalto options 2021-02-26 13:53:26 +01:00
http-set-timeout REGTESTS: Fix required versions for several scripts 2021-01-28 16:37:14 +01:00
log REGTESTS: Fix required versions for several scripts 2021-01-28 16:37:14 +01:00
lua REGTESTS: add a test for the threaded Lua code 2020-12-02 21:53:16 +01:00
mailers CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
mcli REGTEST: mcli/mcli_start_progs: start 2 programs 2020-01-14 15:42:38 +01:00
peers REGTESTS: Send valid URIs in peers reg-tests and fix HA config to avoid warnings 2019-10-14 22:28:50 +02:00
sample_fetches REGTESTS: mark sample_fetches/hashes.vtc as 2.4-only 2021-02-04 18:07:59 +01:00
seamless-reload REGTESTS: mark the abns test as broken again 2020-11-17 11:45:10 +01:00
server REGTESTS: wait for proper return of enable server in cli add server test 2021-03-22 11:52:48 +01:00
spoe CLEANUP: assorted typo fixes in the code and comments 2020-03-14 09:42:07 +01:00
ssl BUG/MINOR: ssl: Fix update of default certificate 2021-03-26 13:06:29 +01:00
stick-table MINOR: stick-tables/counters: add http_fail_cnt and http_fail_rate data types 2021-02-10 12:27:01 +01:00
stickiness REGTESTS: add unresolvable servers to srvkey-addr 2021-01-06 09:20:22 +01:00
stream REGTEST: make the unique-id test depend on version 2.0 2020-04-01 16:08:43 +02:00
webstats REGTEST: rename the reg test files. 2019-04-23 15:37:03 +02:00
README REGTEST: Adapt reg test doc files to vtest. 2019-01-14 14:24:29 +01:00

                 * Regression testing for HAProxy with VTest *


This little README file is about how to compile and run vtest test case files (VTC files)
to test HAProxy for any regression.

To do so, you will have to compile vtest program sources which depends on
Varnish cache application sources. vtest, formerly varnishtest, is a very useful
program which has been developed to test Varnish cache application. vtest has been
modified in collaboration with Varnish cache conceptor Poul-Henning Kamp to support
HAProxy in addition to Varnish cache.

See also: doc/regression-testing.txt

* vtest compilation *

    $ git clone https://github.com/vtest/VTest

    $ cd VTest

    $ make vtest

  Then vtest program may be found at the root directory of vtest sources directory.
  The Varnish cache manuals are located in 'man' directory of Varnish cache sources
  directory. You will have to have a look at varnishtest(7) and vtc(7) manuals to
  use vtest.

  Some information may also be found in doc/regression-testing.txt in HAProxy
  sources.

  Note that VTC files for Varnish cache may be found in bin/varnishtest/tests directory
  of Varnish cache sources directory which may be found here:
  https://github.com/varnishcache/varnish-cache


* vtest execution *

  You must set HAPROXY_PROGRAM environment variable to give the location
  of the HAProxy program to test to vtest:

    $ HAPROXY_PROGRAM=<my haproxy program> vtest [-Dno-htx=] ...

  The HAProxy VTC files found in HAProxy sources may be run with the reg-tests
  Makefile target. You must set the VTEST_PROGRAM environment variable to
  give the location of the vtest program which has been previously compiled.

    $ VTEST_PROGRAM=<my vtest program> make reg-tests

  "reg-tests" Makefile target run scripts/run-regtest.sh script.
  To get more information about this script run it with --help option.

  Note that vtest is run with -t10 and -l option. -l option is to keep
  keep vtest temporary directory in case of failed test cases. core files
  may be found in this directory (if enabled by ulimit).


* vtest patches for HAProxy VTC files *

  When producing a patch to add a VTC regression testing file to reg-tests directory,
  please follow these simple rules:

    - If your VTC file needs others files, if possible, use the same basename as that
      of the VTC file,
    - Put these files in a directory with the same name as the code area concerned
      by the bug ('peers', 'lua', 'acl' etc).