haproxy/reg-tests
Christopher Faulet 9704797fa2 BUG/MEDIUM: http-ana: Properly switch the request in tunnel mode on upgrade
Since the commit f2b02cfd9 ("MAJOR: http-ana: Review error handling during
HTTP payload forwarding"), during the payload forwarding, we are analyzing a
side, we stop to test the opposite side. It means when the HTTP request
forwarding analyzer is called, we no longer check the response side and vice
versa.

Unfortunately, since then, the HTTP tunneling is broken after a protocol
upgrade. On the response is switch in TUNNEL mode. The request remains in
DONE state. As a consequence, data received from the server are forwarded to
the client but not data received from the client.

To fix the bug, when both sides are in DONE state, both are switched in same
time in TUNNEL mode if it was requested. It is performed in the same way in
http_end_request() and http_end_response().

This patch should fix the issue #2125. It is 2.8-specific. No backport
needed.
2023-04-17 16:17:35 +02:00
..
balance REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
cache REGTESTS: cache: Use rxresphdrs to only get headers for 304 responses 2023-02-22 16:12:45 +01:00
checks REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
compression REGTESTS: Remove REQUIRE_VERSION=1.9 from all tests 2023-01-05 09:11:38 +01:00
connection BUG/MEDIUM: mux-h1: Don't release H1 stream upgraded from TCP on error 2022-12-15 09:51:31 +01:00
contrib REGTESTS: Fix prometheus script to perform HTTP health-checks 2022-08-24 12:17:34 +02:00
converter REGTEST: fix the race conditions in hmac.vtc 2023-01-05 15:22:22 +01:00
filters REGTEESTS: filters: Fix CONNECT request in random-forwarding script 2022-07-07 09:52:56 +02:00
http-capture
http-cookies REGTESTS: add test for HTTP/2 cookies concatenation 2022-08-18 16:13:33 +02:00
http-errorfiles
http-messaging BUG/MEDIUM: http-ana: Properly switch the request in tunnel mode on upgrade 2023-04-17 16:17:35 +02:00
http-rules REGTESTS : Add test support for case insentitive for url_param 2023-03-30 15:32:14 +02:00
http-set-timeout
jwt MINOR: jwt: Add support for RSA-PSS signatures (PS256 algorithm) 2023-03-08 10:43:04 +01:00
log REGTESTS: fix the race conditions in log_uri.vtc 2023-04-14 12:13:09 +02:00
lua BUG/MEDIUM: tests: use tmpdir to create UNIX socket 2022-12-18 12:47:20 +01:00
mailers REGTESTS: healthcheckmail: Relax matching on the healthcheck log message 2022-09-12 10:02:27 +02:00
mcli REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
peers REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
sample_fetches
seamless-reload
server MEDIUM: hlua_fcn: dynamic server iteration and indexing 2023-04-05 08:58:16 +02:00
spoe
ssl MINOR: ssl: Accept certpath as param in "show ssl ocsp-response" CLI command 2023-03-14 11:07:32 +01:00
startup REGTESTS: startup: disable automatic_maxconn.vtc 2022-12-16 08:24:04 +01:00
stick-table REGTESTS: fix peers-related regtests regarding "show table" 2022-11-29 16:34:50 +01:00
stickiness REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
stream REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests 2023-01-05 09:11:38 +01:00
tcp-rules
webstats
README

                 * 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 ...

  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).

Please note that most tests use a common set of timeouts defined by the
environment variable HAPROXY_TEST_TIMEOUT. As much as possible, for regular I/O
(i.e. not errors), please try to reuse that setting so that the value may
easily be adjusted when running in some particularly slow environments, or be
shortened to fail faster on developers' machines.