Hi
attached comes a reg-test that can be used to verify that the behaviour
that Patrick described actually exists.
I cannot comment on whether txn:get_priv() is working correctly or not,
this is up to you. The test only checks that the value is reset for the
second request.
Best regards
Tim Düst
On 2018/8/22 05:16, Thierry Fournier wrote:
> Hi Patrick,
>
> Could you retry adding the keyword “local” before data. Unfortunately,
> by default, Lua variables are global.
>
Makes no difference, still get the same result. I don't think it would
do anything anyway as the `txn:get_priv()` will sti
Hi Patrick,
Could you retry adding the keyword “local” before data. Unfortunately, by
default, Lua variables are global.
> core.register_action("test", { "http-req" }, function(txn)
> local data = txn:get_priv()
> if not data then
> data = 0
> end
>
CCing Thierry.
On Tue, Aug 21, 2018 at 11:57:52PM -0400, Patrick Hemmer wrote:
> There is a bug in the current stable haproxy (1.8.13) where the LUA
> function txn:get_priv() is returning data stored from other
> transactions. This was discovered as we have code that triggers on
> certain requests
There is a bug in the current stable haproxy (1.8.13) where the LUA
function txn:get_priv() is returning data stored from other
transactions. This was discovered as we have code that triggers on
certain requests, and it was triggering on requests it should not have been.
You can reproduce with thi
5 matches
Mail list logo
