Awesome, thanks!
czw., 11 maj 2023 o 09:38 Christopher Faulet <cfau...@haproxy.com>
napisał(a):
> Le 5/9/23 à 14:29, Maciej Zdeb a écrit :
> > Hi Christopher,
> > no problem. :) Yes I'm using the same spoe backend for multiple
> frontends. This
> > is my spoe configuration:
> >
> > [abc]
> >
> > spoe-agent abc-agent
> > messages check-abc
> > register-var-names x_abc_request_headers x_headers x_abc_response body
> > option var-prefix abc
> > option set-on-error error
> > option set-total-time total_time
> > timeout hello 100ms
> > timeout idle 41s
> > timeout processing 50ms
> > use-backend spoe-abc
> >
> > spoe-message check-abc
> > args Key=str("123") Key2=str("Haproxy")...
> > acl route_to_abc path_beg -f /etc/haproxy/configs/acl/path_begin.lst
> > event on-frontend-http-request if route_to_abc
> >
>
> Thanks ! I'm able to reproduce the issue.
>
> SPOE filters for disabled proxies are released during startup but pattern
> expressions may be shared between filters. So if the disabled proxy is
> defined
> first, it is an issue because these expressions are released while they
> are
> still used by other filters.
>
> I pushed a fix in 2.8-DEV. It will be backported to all stable versions.
> As a
> workaround, the disabled proxies must not be the first ones defined.
>
> --
> Christopher Faulet
>
>
