RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/reg-tests/server/abnsz.vtc

36 lines
848 B
Plaintext
Raw Normal View History

MEDIUM: socket: add zero-terminated ABNS alternative When an abstract unix socket is bound by HAProxy (using "abns@" prefix), NUL bytes are appended at the end of its path until sun_path is filled (for a total of 108 characters). Here we add an alternative to pass only the non-NUL length of that path to connect/bind calls, such that the effective path of the socket's name is as humanly written. This may be useful to interconnect with existing softwares that implement abstract sockets with this logic instead of the default haproxy one. This is achieved by implementing the "abnsz" socket prefix (instead of "abns"), which stands for "zero-terminated ABNS". "abnsz" prefix may be used anywhere "abns" is. Internally, haproxy uses the custom socket family (AF_CUST_ABNS vs AF_CUST_ABNSZ) to differentiate default abns sockets from zero-terminated ones. Documentation was updated and regtest was added. Fixes GH issues #977 and #2479 Co-authored-by: Aurelien DARRAGON <adarragon@haproxy.com>
2024-10-28 15:23:31 +00:00
varnishtest "Abstract unix socket - zero terminated"
feature ignore_unknown_macro
feature cmd "command -v curl"
# abns@ sockets are not available on freebsd
#EXCLUDE_TARGETS=freebsd,osx,generic
#REGTEST_TYPE=devel
REGTESTS: enable -dW on almost all tests to fail on warnings Now that warnings were almost all removed, let's enable zero-warning via -dW. All tests were adjusted, but two: - mcli/mcli_start_progs.vtc: the programs section currently cannot be silenced - stats/stats-file.vtc: the warning comes from the stats file itself on comment lines. All other ones are now OK.
2024-11-19 06:11:02 +00:00
haproxy h1 -W -S -arg '-dW' -conf {
MEDIUM: socket: add zero-terminated ABNS alternative When an abstract unix socket is bound by HAProxy (using "abns@" prefix), NUL bytes are appended at the end of its path until sun_path is filled (for a total of 108 characters). Here we add an alternative to pass only the non-NUL length of that path to connect/bind calls, such that the effective path of the socket's name is as humanly written. This may be useful to interconnect with existing softwares that implement abstract sockets with this logic instead of the default haproxy one. This is achieved by implementing the "abnsz" socket prefix (instead of "abns"), which stands for "zero-terminated ABNS". "abnsz" prefix may be used anywhere "abns" is. Internally, haproxy uses the custom socket family (AF_CUST_ABNS vs AF_CUST_ABNSZ) to differentiate default abns sockets from zero-terminated ones. Documentation was updated and regtest was added. Fixes GH issues #977 and #2479 Co-authored-by: Aurelien DARRAGON <adarragon@haproxy.com>
2024-10-28 15:23:31 +00:00
global
stats socket "${tmpdir}/h1/stats" level admin expose-fd listeners
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
listen testme
bind "fd@${testme}"
server f2 abnsz@hap-f2
frontend f2
bind abnsz@hap-f2
http-request return status 200 content-type text/plain string "ok"
} -start
client c1 -connect ${h1_testme_sock} {
txreq -url "/"
rxresp
} -run
shell {
curl -sfS --abstract-unix-socket hap-f2 "http://host/" | grep "ok"
}