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/lua/set_var.vtc

53 lines
1.1 KiB
Plaintext
Raw Normal View History

MINOR: lua: Make `set_var()` and `unset_var()` return success This patch makes `set_var()` and `unset_var()` return a boolean indicating success.
2020-05-19 11:49:41 +00:00
varnishtest "Lua: set_var"
REGTESTS: Require the version 2.2 to execute lua/set_var This script depends on LUA changes introduced in HAProxy 2.2 and not backported.
2020-05-26 09:11:23 +00:00
#REQUIRE_VERSION=2.2
MINOR: lua: Make `set_var()` and `unset_var()` return success This patch makes `set_var()` and `unset_var()` return a boolean indicating success.
2020-05-19 11:49:41 +00:00
#REQUIRE_OPTIONS=LUA
feature ignore_unknown_macro
haproxy h1 -conf {
global
lua-load ${testdir}/set_var.lua
frontend fe1
mode http
${no-htx} option http-use-htx
bind "fd@${fe1}"
http-request use-service lua.set_var
MEDIUM: lua: Add `ifexist` parameter to `set_var` As discussed in GitHub issue #624 Lua scripts should not use variables that are never going to be read, because the memory for variable names is never going to be freed. Add an optional `ifexist` parameter to the `set_var` function that allows a Lua developer to set variables that are going to be ignored if the variable name was not used elsewhere before. Usually this mean that there is no `var()` sample fetch for the variable in question within the configuration.
2020-05-19 11:49:42 +00:00
frontend fe2
mode http
${no-htx} option http-use-htx
bind "fd@${fe2}"
http-request set-header Dummy %[var(txn.fe2_foo)]
http-request use-service lua.set_var_ifexist
MINOR: lua: Make `set_var()` and `unset_var()` return success This patch makes `set_var()` and `unset_var()` return a boolean indicating success.
2020-05-19 11:49:41 +00:00
} -start
client c0 -connect ${h1_fe1_sock} {
txreq -url "/" \
MEDIUM: lua: Add `ifexist` parameter to `set_var` As discussed in GitHub issue #624 Lua scripts should not use variables that are never going to be read, because the memory for variable names is never going to be freed. Add an optional `ifexist` parameter to the `set_var` function that allows a Lua developer to set variables that are going to be ignored if the variable name was not used elsewhere before. Usually this mean that there is no `var()` sample fetch for the variable in question within the configuration.
2020-05-19 11:49:42 +00:00
-hdr "Var: txn.fe1_foo"
MINOR: lua: Make `set_var()` and `unset_var()` return success This patch makes `set_var()` and `unset_var()` return a boolean indicating success.
2020-05-19 11:49:41 +00:00
rxresp
expect resp.status == 202
expect resp.http.echo == "value"
txreq -url "/" \
-hdr "Var: invalid.var"
rxresp
expect resp.status == 400
expect resp.http.echo == "(nil)"
} -run
MEDIUM: lua: Add `ifexist` parameter to `set_var` As discussed in GitHub issue #624 Lua scripts should not use variables that are never going to be read, because the memory for variable names is never going to be freed. Add an optional `ifexist` parameter to the `set_var` function that allows a Lua developer to set variables that are going to be ignored if the variable name was not used elsewhere before. Usually this mean that there is no `var()` sample fetch for the variable in question within the configuration.
2020-05-19 11:49:42 +00:00
client c1 -connect ${h1_fe2_sock} {
txreq -url "/" \
-hdr "Var: txn.fe2_foo"
rxresp
expect resp.status == 202
expect resp.http.echo == "value"
txreq -url "/" \
-hdr "Var: txn.fe2_bar"
rxresp
expect resp.status == 400
expect resp.http.echo == "(nil)"
} -run