REGTEST: Don't use the websocket to validate http-check

Now, some conformance tests are performed when an HTTP connection is
upgraded to websocket. This make the http-check-send.vtc script failed for
the backend <be6_ws>. Because the purpose of this health-check is to pass a
"Connection: Upgrade" header on an http-check send rule, we may use a dummy
protocal instead.
This commit is contained in:
Christopher Faulet 2021-01-05 15:42:51 +01:00
parent 85a813676f
commit d2dcd8a88f

View File

@ -72,11 +72,11 @@ server s6 {
expect req.proto == HTTP/1.1
expect req.http.host == "ws-host"
expect req.http.connection == "upgrade"
expect req.http.upgrade == "websocket"
expect req.http.upgrade == "raw-proto"
txresp \
-status 101 \
-hdr "connection: upgrade" \
-hdr "upgrade: websocket"
-hdr "upgrade: raw-proto"
} -start
@ -154,7 +154,7 @@ haproxy h1 -conf {
backend be6_ws
log ${S6_addr}:${S6_port} len 2048 local0
http-check send meth GET uri / ver HTTP/1.1 hdr host ws-host hdr connection upgrade hdr upgrade websocket
http-check send meth GET uri / ver HTTP/1.1 hdr host ws-host hdr connection upgrade hdr upgrade raw-proto
http-check expect status 101
server srv ${s6_addr}:${s6_port} check inter 200ms rise 1 fall 1